Address Poisoning Check
Before sending crypto, check the recipient for address poisoning: lookalikes and bad checksums
Open the source (opens github.com) https://github.com/devx-agent/address-poisoning-check
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
What it is
MCP servers from io.github.devx-agent.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
devx-address-poisoning-check@1.1.0
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://address-poisoning-check.nextill-pos.workers.dev/mcp
From the server's entry in the official MCP Registry
Related
-
Onyx AML
MCP serversCrypto address risk checks for agents: USDT/USDC blacklists, sanctions, scam lists, poisoning
-
Trust Check
MCP serversBase crypto safety for agents: honeypot/tax test, address poisoning, rug feed, creator record.
-
Execute data-poisoning-detector-mcp
MCP serversPremium agentic endpoint for data-poisoning-detector-mcp.
-
memory-poisoning-scanner
MCP serversScans agent code for untrusted input poisoning persistent cross-session memory
@guardbee/mcp-memory-poisoning-scanner@0.1.2 -
memory-poisoning-scanner
MCP serversScans agent code for untrusted input poisoning persistent cross-session memory
@guardbee/mcp-memory-poisoning-scanner@0.3.1 -
rag-embedding-poisoning-escrow-auditor
MCP serversERC-8183 RAG Knowledge Base & Vector Embedding Anti-Poisoning Auditor & Escrow on Base.