Local MCP capabilities provider for Expo
Nothing to run from here
DeepCounterfeit 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.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Solana pre-buy check, smart-money flow and imitation detection. Free tier; x402 pay-per-call.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http deepcounterfeit-mcp https://deepcounterfeit.com/mcp
# 2 — ask your agent for something these tools do
# check_token, check_name, search_alerts and 5 more
DeepCounterfeit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DEAll 1 server
deepcounterfeit1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 deepcounterfeit-mcp https://deepcounterfeit.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take X-API-Key header (Optional API key from https://deepcounterfeit.com/signup for real-time data. Omit for the free tier (5 calls/min, 24 h delayed).) if you want to set it.
What it writes
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.
What you approve
8 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.
Look up a deployed token by contract/mint address and report whether it impersonates a real company, its "official" token or its tokenized stock (e.g. a fake SpaceX, Coinbase or NVDAx coin). Returns verdict (likely_impersonation | brand_mention_watch | not_in_index), matched brands, risk score 0-100 with reasons (creator bought supply at launch, same-block bundles, creator cash-out, serial launche
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Token mint (Solana) or contract address (0x... on BNB Chain, Base, Robinhood Chain). |
| chain | string | no | Optional chain filter. |
Run the impersonation detector on a token name and/or ticker symbol without needing an address. Tells you whether a coin called e.g. "SpaceX Official" ($SPACEX) or "TSLAx" would be flagged as impersonating a brand, which brand, and why. Use for pre-launch name checks, or when a user mentions a coin by name and you have no address (with an address, use check_token). Does not assess creator behaviou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Token name, e.g. "Coinbase Official Token". |
| symbol | string | no | Ticker symbol without $, e.g. "COIN". |
| description | string | no | Optional token description text. |
List recent impersonation coins, newest first, filtered by brand, chain, time and severity. Use to answer "are there fake <brand> tokens?", to monitor a brand, or to collect cases for a takedown. Free tier returns alerts older than 24 h only (max 20).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand | string | no | Brand id, name, or ticker, e.g. "spacex", "SpaceX", "TSLA". See list_brands. |
| chain | string | no | Optional chain filter (bsc = BNB Chain, robinhood = Robinhood Chain). Omit for all chains. |
| since | string | no | Start time: relative ("24h", "7d", "30m"), ISO 8601 ("2026-10-01") or unix seconds. |
| severity | string | no | high = risk 70+, medium = 50-69. |
| min_risk | integer | no | Only alerts with risk score >= this (needs an API key; ignored on the keyless Free tier). |
| include_watch | boolean | no | Also include watch-tier brand mentions (memes), not just impersonation alerts. |
| limit | integer | no | Max alerts to return (Free tier capped at 20). Narrow with since/brand instead of paging. |
Summarise impersonation activity against one brand over a window: number of fake coins, traded volume, breakdown by chain/match type/severity, repeat creator wallets, how many creators bought 50%+ of supply, and the top cases with evidence. Pro/Wholesale keys also get the takedown-ready PDF link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand | string | yes | Brand id, name or ticker, e.g. "anthropic", "Coinbase", "NVDA". |
| days | number | no | Look-back window in days. |
List the brands on the watchlist (companies, tokenized stocks, crypto projects, private companies) with ids, tickers and all-time alert counts, most-targeted first. Use to find a brand id or check whether a brand is covered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional substring of name, id, alias or ticker. |
| category | string | no | Optional: sp500, xstock, crypto, private, foreign, consumer, media, finance, sports, stock. |
| limit | integer | no | Max brands to return, most-targeted first. |
Aggregate numbers for a window: alerts, high-severity count, brands hit, by chain, by match type, top brands, data-source health and coverage. Use for overviews, trend questions and to check data freshness.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | number | no | Window in days (1 = last 24 h). |
Search the impersonation index by brand name, ticker or coin name. Returns result ids for fetch. Prefer search_alerts / check_name when available.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Brand name/ticker (e.g. "SpaceX", "TSLA") or part of a coin name. Brand matches return that brand's latest alerts; otherwise coin names are substring-matched. |
Fetch the full check_token result for a result id returned by search (format "<chain>:<address>"): verdict, matched brands, match type and explorer links; with an API key also risk score, reasons and creator facts. Use after search; for a known address call check_token directly.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Result id from search, e.g. "solana:<mint>" or "bsc:0x...". |
Free
$0 forever
- 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 DeepCounterfeit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest1c00125dde9808ad52c7e6d2442ce9f7b42e0f6ac925d45fcaca0982706624bf
Score vectorthreat 100 → client 96
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| check_token | no tags | |
| check_name | no tags | |
| search_alerts | no tags | |
| get_brand_report | no tags | |
| list_brands | no tags | |
| get_stats | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
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
Integrityfirst-seen
Surface digest1c00125dde9808ad
Scanned2026-10-28
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 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish DeepCounterfeit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.