devx-address-poisoning-check
Hosted as a Cloudflare Worker that provides the remote MCP endpoint and HTTP API for address-poisoning checks.
Uses Coinbase CDP SQL API for Base ERC-20 transfer history and the Coinbase CDP facilitator for x402 USDC payments on Base, enabling paid on-chain address-poisoning checks.
Scans a sender's Ethereum token transfers and transactions to detect address-poisoning lookalikes, zero-value/dust/fake-token transfers, and senders that may already have been poisoned.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@devx-address-poisoning-check is 0xd9A1C3788D81257612E2581A6ea0aDa244853a91 a poisoning lookalike?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Address Poisoning Check
Is this the address you meant? Address poisoning plants a lookalike address (same first and last characters, different middle) in a wallet's history with a zero-value, dust or fake-token transfer, and waits for the owner (or their AI agent) to copy it. Bitquery counted about $76M stolen on Ethereum alone in the 12 months to July 2026.
This repo has three pieces, all read-only (we never ask for keys and never move funds):
What | Cost | |
CLI / stdio MCP | Offline: is the recipient a lookalike of any address you trust? Is its EIP-55 checksum valid? Nothing leaves your machine. | free |
Remote MCP | Same offline check as a hosted MCP tool | free |
HTTP API | On-chain: scans the sender's real transfer history (Ethereum + Base, optional Avalanche) and flags lookalikes of real counterparties, zero-value / dust / fake-token poisoning transfers (with tx hashes), recipients that only ever appeared through such transfers, and senders that were already poisoned. Returns | 0.005 USDC via x402 on Base |
Live: https://address-poisoning-check.nextill-pos.workers.dev
CLI
npx devx-address-poisoning-check 0xd9A1C3788D81257612E2581A6ea0aDa244853a91 --known 0xd9A1b0B1e1aE382DbDc898Ea68012FfcB2853a91
# DANGER: Looks like 0xd9a1...3a91 (same first 4 / last 6 hex chars) but is a different address. Classic address-poisoning lookalike.Exit code 2 on danger, so it can gate scripts and agent payment flows.
Related MCP server: Cybercentry MCP Server
MCP
Claude Desktop / Cursor (stdio):
{ "mcpServers": { "address-poisoning-check": { "command": "npx", "args": ["-y", "devx-address-poisoning-check", "mcp"] } } }Or remote (streamable HTTP): https://address-poisoning-check.nextill-pos.workers.dev/mcp
Tools: check_recipient_lookalike (free), onchain_check_info (how to buy the on-chain check; does not pay).
Paid on-chain check (x402)
GET https://address-poisoning-check.nextill-pos.workers.dev/v1/check?from=0x...&to=0x...[&chains=ethereum,base,avalanche]Answers
402with an x402 v1 body (X-PAYMENT, networkbase) and a v2PAYMENT-REQUIREDheader (PAYMENT-SIGNATURE,eip155:8453). Both work.5000 atomic USDC (0.005 USDC) to
0xB3cDDccEe6B150c8efFD55B961afc0Ecefe7f247, settled through the Coinbase CDP facilitator, listed in the CDP x402 Bazaar.Settled only after the report is produced; bad input or data-source errors are not charged.
Data: Ethereum/Avalanche via the Routescan explorer API (last 300 token transfers + 150 transactions of the sender); Base via the Coinbase CDP SQL API (last 14 days of all ERC-20 transfers, including unknown/fake tokens), falling back to public RPC logs for a shorter window. Typical paid response: about 1-2 s. Data collection has a 3.5 s budget; if a source is slow you still get a report with
"partial": trueand the scanned window stated per chain inchains[].window. It is a heuristic over a window of public data: always confirm the full address with the payee.
Example (the May 2024 $68M WBTC case): from=0x1E227979f0b5BC691a70DEAed2e0F39a6F538FD5&to=0xd9A1C3788D81257612E2581A6ea0aDa244853a91 returns danger / possibly_already_poisoned: the victim did send real value to that address, but it first appeared in their history through a zero-value transfer.
OpenAPI: /openapi.json · Terms: /terms
Related DevX tools
7702 Sweeper Check: is an EIP-7702 sweeper delegation set on a wallet?
Crypto Link Check: is a crypto URL a phishing / drainer lookalike?
Repo Run Check: is a GitHub repo safe to clone and run?
Layout
cli/: npm packagedevx-address-poisoning-check(CLI + stdio MCP),npm testworker/: the Cloudflare Worker behind the hosted API (npm run build)
MIT. Made by DevX · madebydevx@gmail.com
Available Tools
2 toolscheck_recipient_lookalikeCheck a recipient for address poisoningARead-onlyIdempotentInspect
Compares the EVM address you are about to pay with addresses you trust and checks its EIP-55 checksum, to catch address-poisoning lookalikes before a transfer. Address poisoning: attackers send tiny or zero-value transfers from an address that shares the first and last hex characters with one of your real payees, hoping you copy it from your history. Use this tool before every transfer to an address that was pasted or copied, especially from wallet or explorer history. Offline and deterministic: nothing leaves the machine, no RPC calls, no keys, no signing. Rules: a lookalike shares at least 3 leading and 3 trailing hex characters with a trusted address (or 8 in total with at least 2 on each side) but is not identical. A mixed-case address whose EIP-55 checksum fails is treated as altered or mistyped. All-lowercase or all-uppercase input has no checksum (checksum_valid null). Returns: verdict (match = identical to a trusted address; danger = lookalike of a trusted address or invalid checksum: do not send; unknown = no match and no lookalike, which only means it is not similar to the addresses you supplied), a note, checksum_valid, compared, matches, lookalikes (address, shared_prefix, shared_suffix, shown_as) and onchain_check (URL of the paid history-based check). This tool only knows the addresses you pass in. To scan the sending wallet's real on-chain transfer history for poisoning transfers, see onchain_check_info.
Inputs: to (required), known. Returns: to, note, matches, verdict, +4 more
onchain_check_infoHow to buy the on-chain poisoning checkARead-onlyIdempotentInspect
Returns the endpoint, price and payment method of the optional paid hosted check. It does not call the API and does not pay or sign anything. The paid check reads the sending wallet's real transfer history on Ethereum and Base (optionally Avalanche), finds poisoning transfers (zero-value, dust or fake-token transfers from lookalike addresses) and returns a verdict ok | caution | danger, the address you probably meant, and evidence transaction hashes. It costs 0.005 USDC on Base via x402. Use it when you have no trusted address list to pass to check_recipient_lookalike, or when check_recipient_lookalike returns unknown for a recipient copied from transaction history. Returns: method, url_template, price_usdc, network, asset, protocol, chains, settles and docs.
Inputs: no named parameters. Returns: docs, asset, chains, method, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly separate roles: one performs the offline lookalike/checksum check, while the other only returns metadata about an optional paid on-chain service. Their names and descriptions make it hard to confuse the action tool with the informational tool.
Both names use snake_case and are descriptive, but they do not follow a uniform verb_noun pattern: check_recipient_lookalike is action-oriented, while onchain_check_info is an info getter. This is a minor deviation rather than inconsistent style.
Only two tools are provided, which feels thin even for a narrow pre-transfer address-checking server. The count is defensible because one tool does the main check and the other explains an optional paid alternative, but the surface is borderline minimal.
The core offline lookalike and checksum check is covered, but the on-chain history scan is not exposed as a callable tool, only as endpoint metadata. That is a notable gap for a server framed around address-poisoning detection, requiring an external paid workflow to complete the lifecycle.
Maintenance
Related MCP Connectors
Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.
Token rug-risk scans, Know Your Agent wallet checks and deployer reputation for AI agents.
Safety checks before you sign, pay or install: contract, token and package scans, phishing, OFAC.
Crypto transaction safety tool — screens addresses and transactions for scam risk.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to scan crypto transactions for scam addresses, clipboard-hijack patterns, and typos, as well as report scam addresses and check usage, directly in conversation.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.2MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to assess the risk of crypto wallets, tokens, and smart contracts by providing read-only on-chain analysis, 0-100 risk scoring with explanations, fund tracing, and contract inspection before interaction.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check a payment recipient against the sender's own on-chain history before funds move, flagging address-poisoning look-alikes, spoofed 'from you' transfers, and fake tokens via the Blockscout PRO API. It also scans a wallet for poisoning attempts aimed at it, returning a verdict of OK, CAUTION, or STOP.MIT