A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Exclusive Digits phone numbers is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search US local phone numbers for sale by city, area code, word, pattern or price.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http exclusive-digits-phone-numbers-mcp https://exclusivedigits.com/mcp
# 2 — ask your agent for something these tools do
# find_numbers, get_number, catalog_vocabulary and 1 more
Exclusive Digits phone numbers costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http exclusive-digits-phone-numbers-mcp https://exclusivedigits.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Searches Exclusive Digits' phone numbers for sale and returns up to 20, ranked best first, each with price, location, what it spells, its patterns and its page link. Unknown pattern or industry codes are left out with a note. When nothing matches, the search widens on its own and the reply says how.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request | string | no | The user's request in their own words, e.g. "an easy to remember number for my Austin plumbing business under $300". The store checks your other fields against these words and the fields themselves. |
| place_words | string | no | The words that name the place: "Miami", "south Florida", "NYC", "Austin, TX", "90210". Leave out when no place was named. |
| state | string | no | Two-letter US state of that place, or the state asked for ("TX"). |
| area_codes | array | no | Area codes that serve the place, overlays included (Miami: 305, 786, 645; Manhattan: 212, 646, 332, 917), or an area code the user asked for. A city with no area codes searches its whole state, so giv |
| words | array | no | What the number should spell, letters only, 3 to 7 letters (PIZZA, not "pizza place"). One is usual. |
| alternate_words | array | no | Short words with the same meaning, tried when the first finds nothing (PIZZA: PIE, SLICE). |
| digits | string | no | 3 to 7 digits the number should contain ("7777"), not an area code asked for as a place. |
| position | string | no | Where the word or digits go: endsWith (the default), startsWith (right after the area code; needs a place) or contains (anywhere). |
| industry | string | no | Industry code when the user names a kind of business and no word, e.g. LAW, MED, REAL, HOME, AUTO. catalog_vocabulary lists them all. |
| pattern | string | no | Pattern code when the user describes one: repeating ("easy to remember"), lucky_sevens ("lots of 7s"), npa_nxx_x000 ("ends in 000"), sequential, year. catalog_vocabulary lists them all. |
| min_price | number | no | Lowest price in US dollars. |
| max_price | number | no | Highest price in US dollars ("under $500" is 500). |
| sort | string | no | recommended (the default ranking), price_asc for "cheap", price_desc for "premium", newest. |
| own_numbers_only | boolean | no | Only numbers the store owns itself. |
| on_sale | boolean | no | Only numbers on sale, including daily specials. |
| search_id | string | no | The search_id of an earlier result, with page, for more numbers from that search. Send no other fields with it. |
| page | integer | no | Page 2 to 5 of the search named by search_id. |
Return the current price, availability, location, named patterns and page link for one ten-digit US phone number.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | yes | A ten-digit US phone number; punctuation is allowed. |
List the pattern codes (with names and examples) and industry codes find_numbers accepts.
No parameter schema on file.
How to buy, the one-time price, when the card is charged, what the buyer receives, transfer time to their carrier, refunds and support.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Exclusive Digits phone numbers or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_numbers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_number | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| catalog_vocabulary | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| how_buying_works | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Exclusive Digits phone numbers can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.