token_verdict — forensics mcp MCP Tool
token_verdict
(token verdict) is one of 6 tools on the
forensics mcp
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 forensics mcp token_verdict run in your project directory
- Claude Desktop forensics mcp token_verdict ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor forensics mcp token_verdict ~/.cursor/mcp.json
- VS Code forensics mcp token_verdict .vscode/mcp.json
- Zed forensics mcp token_verdict ~/.config/zed/settings.json
- Windsurf forensics mcp token_verdict ~/.codeium/windsurf/mcp_config.json
- Cline forensics mcp token_verdict ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI forensics mcp token_verdict ~/.gemini/settings.json
- Grok forensics mcp token_verdict .mcp.json (in your project root)
- ChatGPT forensics mcp token_verdict Settings → Connectors → Advanced → Developer mode
- Claude.ai forensics mcp token_verdict Settings → Connectors → Add custom connector
- LangChain forensics mcp 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 20 October 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.