Address Poisoning Check MCP Server

by devx-agent Your server? Claim it

answering

Address Poisoning Check is answering right now. Last checked moments ago. It exposes 2 tools. Last commit 30 Oct 2026.

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

Uptime history 71 hours of history

71 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

93 ms

Response time

average over 24h

Stars

last commit 30 Oct 2026

Nothing serious here today

Today is the operative word: we check Address Poisoning Check every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add address-poisoning-check --transport http https://address-poisoning-check.nextill-pos.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://address-poisoning-check.nextill-pos.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.address-poisoning-check]
url = "https://address-poisoning-check.nextill-pos.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "address-poisoning-check": {
      "url": "https://address-poisoning-check.nextill-pos.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "address-poisoning-check": {
      "type": "http",
      "url": "https://address-poisoning-check.nextill-pos.workers.dev/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

onchain

onchain_check_info

How to buy the on-chain check (scans the sender's real transfer history on Ethereum/Base/Avalanche for poisoning transfers and lookalikes) via x402 for 0.005 USDC. Does not pay.

recipient

check_recipient_lookalike

Free, offline, read-only: before sending crypto, check whether the recipient address is a lookalike (same first/last hex characters, different middle) of any address you trust, and whether its EIP-55 checksum is valid. Address poisoning stole $76M+ in 12 months by planting such lookalikes in wallet histories.

Endpoints

URL	Transport	State	Latency	Checked
https://address-poisoning-check.nextill-pos.workers.dev/mcp	streamable-http	answering	51 ms	0 min ago

Alternatives to Address Poisoning Check

same job, measured the same way

Payment Guard MCP

by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

94 installs/wk local only

Trust Check

by gmahar82-stack

Base crypto safety for agents: honeypot/tax test, address poisoning, rug feed, creator record.

5 tools answering

Crypto Link Check

by devx-agent

Check crypto links for phishing lookalikes of wallets, exchanges and dapps before wallet connect

2 tools answering

Onyx AML

by onyxprotocol

Crypto address risk checks for agents: USDT/USDC blacklists, sanctions, scam lists, poisoning

8 tools answering

SaveSaveSaveSave

by stefantsezarov

Check messages, npm packages and crypto addresses before acting. Read-only scanner tools.

70 installs/wk local only

Sentinel

by 448c

Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.

50 tools answering

ASPERN: counterparty checks for agents

by aspern

What the chain records about an address before you pay it, and whether a payment fits it.

40 tools answering

UK Sanctions Screening MCP

by donniertf-hub

Screen names vs the UK Sanctions List (FCDO/OFSI) plus OFAC crypto address checks.

12 tools answering

Address Poisoning Check — questions

Answers built from our own checks of this server.

What can Address Poisoning Check do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_recipient_lookalike, onchain_check_info. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Address Poisoning Check working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 93 ms. The bar chart above shows every period we have measured.

How do I connect Address Poisoning Check?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Address Poisoning Check need an API key?

No. Address Poisoning Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Address Poisoning Check?

It answers our handshake in 93 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Address Poisoning Check open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at address-poisoning-check.nextill-pos.workers.dev, which runs on its operator's own terms.