Address Poisoning Check

io.github.devx-agent由 GitHub 账号 devx-agent 发布v1.1.0更新于 Nov 6, 2026

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

发布方自己的服务:check.tattoo: tattoo size and placement guide

已验证Streamable HTTP可网页运行金融安全与监控

概览

AI 生成的概览

只读 MCP 服务器,在转账前检查加密收款地址是否为地址投毒仿冒地址,并校验 EIP-55 校验和。

可以做什么
  • 将收款地址与你信任的地址比对,识别首尾十六进制字符相同、中间不同的仿冒地址,并校验 EIP-55 校验和,离线且免费。
  • 提供付费链上检查的购买说明,该检查会扫描发送方在以太坊、Base 及可选 Avalanche 上的转账历史,找出投毒转账与仿冒地址;该工具本身不付款。
  • 既可通过 npm 命令行或 stdio 服务器在本地运行同样的免费检查,也可使用托管远程端点。
适用场景
适合在助手协助准备或把关加密转账时,确认收款地址不是已知交易对手的仿冒地址。也适用于需要在发送前获得风险信号的脚本化或代理支付流程。
运行要求
需要远程 streamable HTTP 端点,或本地安装 Node.js 以通过 npx 运行 npm 包。未声明任何账户、API 密钥或环境变量。付费链上检查是独立的 HTTP API,通过 Base 上的 x402 以 USDC 计费。
安装前请注意
免费仿冒检查仅基于地址前后缀的启发式判断,不能证明地址正确,请与收款方核对完整地址。链上检查每次调用需通过 Base 上的 x402 支付 0.005 USDC,需要支持支付的客户端。服务器声明为只读且从不索取私钥,但任何情况下都不要向工具提供私钥或助记词。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Address Poisoning Check,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.devx-agent%2Faddress-poisoning-check/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

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):

WhatCost
CLI / stdio MCP devx-address-poisoning-checkOffline: is the recipient a lookalike of any address you trust? Is its EIP-55 checksum valid? Nothing leaves your machine.free
Remote MCP https://address-poisoning-check.nextill-pos.workers.dev/mcpSame offline check as a hosted MCP toolfree
HTTP API GET /v1/check?from=<sender>&to=<recipient>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 ok | caution | danger and the address you probably meant.0.005 USDC via x402 on Base

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

CLI

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

MCP

Claude Desktop / Cursor (stdio):

json
{ "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 402 with an x402 v1 body (X-PAYMENT, network base) and a v2 PAYMENT-REQUIRED header (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": true and the scanned window stated per chain in chains[].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

Layout

  • cli/: npm package devx-address-poisoning-check (CLI + stdio MCP), npm test
  • worker/: the Cloudflare Worker behind the hosted API (npm run build)

MIT. Made by DevX · [email protected]

来源:README.md,提交 2141d56

工具

2

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.

输入参数to必填known

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.

无需输入参数。

版本历史

1
  1. v1.1.0最新Oct 30, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Check 集成