onchain_check_info — Address Poisoning Check MCP Tool
onchain_check_info
(onchain check info) is one of 2 tools on the
Address Poisoning Check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call onchain_check_info from your client
- Claude Code Address Poisoning Check onchain_check_info run in your project directory
- Claude Desktop Address Poisoning Check onchain_check_info ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Address Poisoning Check onchain_check_info ~/.cursor/mcp.json
- VS Code Address Poisoning Check onchain_check_info .vscode/mcp.json
- Zed Address Poisoning Check onchain_check_info ~/.config/zed/settings.json
- Windsurf Address Poisoning Check onchain_check_info ~/.codeium/windsurf/mcp_config.json
- Cline Address Poisoning Check onchain_check_info ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Address Poisoning Check onchain_check_info ~/.gemini/settings.json
- Grok Address Poisoning Check onchain_check_info .mcp.json (in your project root)
- ChatGPT Address Poisoning Check onchain_check_info Settings → Connectors → Advanced → Developer mode
- Claude.ai Address Poisoning Check onchain_check_info Settings → Connectors → Add custom connector
- LangChain Address Poisoning Check onchain_check_info pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http address-poisoning-check https://address-poisoning-check.nextill-pos.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.