token_verdict — On-chain Forensics MCP Tool
token_verdict
(token verdict) is one of 6 tools on the
On-chain Forensics
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call token_verdict from your client
- Claude Code On-chain Forensics token_verdict run in your project directory
- Claude Desktop On-chain Forensics token_verdict ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor On-chain Forensics token_verdict ~/.cursor/mcp.json
- VS Code On-chain Forensics token_verdict .vscode/mcp.json
- Zed On-chain Forensics token_verdict ~/.config/zed/settings.json
- Windsurf On-chain Forensics token_verdict ~/.codeium/windsurf/mcp_config.json
- Cline On-chain Forensics token_verdict ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI On-chain Forensics token_verdict ~/.gemini/settings.json
- Grok On-chain Forensics token_verdict .mcp.json (in your project root)
- ChatGPT On-chain Forensics token_verdict Settings → Connectors → Advanced → Developer mode
- Claude.ai On-chain Forensics token_verdict Settings → Connectors → Add custom connector
- LangChain On-chain Forensics token_verdict pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http forensics-mcp https://solene-fa2010da.base44.app/functions/forensicsMcpOther 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.