# Address Poisoning Check (npm · devx-address-poisoning-check)

Before sending crypto, check the recipient for address poisoning: lookalikes and bad checksums

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `address-poisoning-check.nextill-pos.workers.dev`: 69/100, [markdown](https://verifymcp.io/servers/devx-agent-address-poisoning-check/address-poisoning-check.md), [page](https://verifymcp.io/servers/devx-agent-address-poisoning-check/address-poisoning-check)
- npm · `devx-address-poisoning-check`: 63/100 (this document), [markdown](https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check.md), [page](https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check)

## Channel facts

- Registry: `npm`
- Package: `devx-address-poisoning-check`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add devx-agent-address-poisoning-check -- npx -y devx-address-poisoning-check mcp
```

### Cursor

```json
{
  "mcpServers": {
    "devx-agent-address-poisoning-check": {
      "command": "npx",
      "args": [
        "-y",
        "devx-address-poisoning-check",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "devx-agent-address-poisoning-check": {
      "command": "npx",
      "args": [
        "-y",
        "devx-address-poisoning-check",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add devx-agent-address-poisoning-check -- npx -y devx-address-poisoning-check mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "devx-agent-address-poisoning-check": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "devx-address-poisoning-check",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add devx-agent-address-poisoning-check --command npx --arg -y --arg devx-address-poisoning-check --arg mcp
```

### Hermes

```yaml
mcp_servers:
  devx-agent-address-poisoning-check:
    command: "npx"
    args: ["-y", "devx-address-poisoning-check", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "devx-agent-address-poisoning-check": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "devx-address-poisoning-check",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add devx-agent-address-poisoning-check -t stdio -c npx -a -y devx-address-poisoning-check mcp
```

### Other

```json
{
  "mcpServers": {
    "devx-agent-address-poisoning-check": {
      "command": "npx",
      "args": [
        "-y",
        "devx-address-poisoning-check",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 63, +20)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: unverified → fail
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → 0.86

### 2026-10-30 (score 43)

First indexed and scored.

## MCP tools (2)

### `check_recipient_lookalike` (~417 tokens)

Check a recipient for address poisoning

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.

Input parameters:

- `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, required): 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.

Output parameters:

- `checksum_valid` (boolean|null): true valid, false invalid, null when the input has no checksum (single case)
- `compared` (number): number of trusted addresses compared
- `lookalikes` (array)
- `matches` (array)
- `note` (string)
- `onchain_check` (string)
- `to` (string): recipient, lowercased
- `verdict` (string)

### `onchain_check_info` (~174 tokens)

How to buy the on-chain poisoning check

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.

Output parameters:

- `asset` (string)
- `chains` (array)
- `docs` (string)
- `method` (string)
- `network` (string)
- `price_usdc` (number)
- `protocol` (string)
- `settles` (string)
- `url_template` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 43

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/devx-address-poisoning-check
- Socket report: https://socket.dev/npm/package/devx-address-poisoning-check
- Repository: https://github.com/devx-agent/address-poisoning-check
- Website: https://address-poisoning-check.nextill-pos.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check.xml
- Changelog JSON feed: https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check.json
- HTML version of this page: https://verifymcp.io/servers/devx-agent-address-poisoning-check/devx-address-poisoning-check