scan_token_forensics — NullClear Arbiter MCP Tool
scan_token_forensics
(scan token forensics) is one of 13 tools on the
NullClear Arbiter
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call scan_token_forensics from your client
- Claude Code NullClear Arbiter scan_token_forensics run in your project directory
- Claude Desktop NullClear Arbiter scan_token_forensics ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NullClear Arbiter scan_token_forensics ~/.cursor/mcp.json
- VS Code NullClear Arbiter scan_token_forensics .vscode/mcp.json
- Zed NullClear Arbiter scan_token_forensics ~/.config/zed/settings.json
- Windsurf NullClear Arbiter scan_token_forensics ~/.codeium/windsurf/mcp_config.json
- Cline NullClear Arbiter scan_token_forensics ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NullClear Arbiter scan_token_forensics ~/.gemini/settings.json
- Grok NullClear Arbiter scan_token_forensics .mcp.json (in your project root)
- ChatGPT NullClear Arbiter scan_token_forensics Settings → Connectors → Advanced → Developer mode
- Claude.ai NullClear Arbiter scan_token_forensics Settings → Connectors → Add custom connector
- LangChain NullClear Arbiter scan_token_forensics pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nullclear https://api.nullclear.dev/mcpOther tools on this server
- inspect_contract_abi_and_proxy
- decode_calldata_or_failed_tx
- simulate_transaction_preflight
- read_url_clean_markdown
- nullclear_discover_verified_x402_apis
- nullclear_token_security_audit
- nullclear_wallet_risk_score
- nullclear_crypto_market_oracle
- nullclear_safe_fetch
- nullclear_escrow_x402_call
- nullclear_check_reputation
- nullclear_verify_kya_mandate
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.