Address Poisoning Check
NPM · DEVX-ADDRESS-POISONING-CHECK · 2 COMPONENTS
Before sending crypto, check the recipient for address poisoning: lookalikes and bad checksums
Last scanned (13 hours ago)
Scores higher than 31% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 682 tokens (~341/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +20
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 30 Oct 26 43
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/devx-address-poisoning-check@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_recipient_lookalike Check a recipient for address poisoning ~417
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.
| Name | Type | Req | Description |
|---|---|---|---|
| known | array | – | Up to 200 addresses you trust, for example the address book and previous real payees, each 0x + 40 hex. With an empty list only the checksum is checked. |
| to | string | yes | The recipient you are about to send to: 0x followed by 40 hex characters. Pass it exactly as copied, keeping its letter case, so the EIP-55 checksum can be checked. |
| Name | Type | Req | Description |
|---|---|---|---|
| checksum_valid | boolean|null | yes | true valid, false invalid, null when the input has no checksum (single case) |
| compared | number | yes | number of trusted addresses compared |
| lookalikes | array | yes | – |
| matches | array | yes | – |
| note | string | yes | – |
| onchain_check | string | yes | – |
| to | string | yes | recipient, lowercased |
| verdict | string | yes | – |
No examples provided.
onchain_check_info How to buy the on-chain poisoning check ~174
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| chains | array | yes | – |
| docs | string | yes | – |
| method | string | yes | – |
| network | string | yes | – |
| price_usdc | number | yes | – |
| protocol | string | yes | – |
| settles | string | yes | – |
| url_template | string | yes | – |
No examples provided.
How do I install the Address Poisoning Check MCP server?
Address Poisoning Check runs locally as an npm package, launched with npx -y devx-address-poisoning-check mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · devx-address-poisoning-check
claude mcp add devx-agent-address-poisoning-check -- npx -y devx-address-poisoning-check mcp
What is the Address Poisoning Check MCP server?
Address Poisoning Check is an MCP server listed in the public MCP registry as io.github.devx-agent/address-poisoning-check. Before sending crypto, check the recipient for address poisoning: lookalikes and bad checksums. This page covers its npm package (devx-address-poisoning-check).
Is the Address Poisoning Check MCP server safe to use?
Address Poisoning Check scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Address Poisoning Check MCP server expose?
Address Poisoning Check exposes 2 tools: check_recipient_lookalike, onchain_check_info. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Is the Address Poisoning Check MCP server still maintained?
Address Poisoning Check is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Address Poisoning Check MCP server under?
Address Poisoning Check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Address Poisoning Check MCP server?
VerifyMCP ran 15 checks on Address Poisoning Check, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Address Poisoning Check: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.