analyze_token — bitfence Risk Oracle MCP Tool
analyze_token
(analyze token) is one of 2 tools on the
bitfence Risk Oracle
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_token from your client
- Claude Code bitfence Risk Oracle analyze_token run in your project directory
- Claude Desktop bitfence Risk Oracle analyze_token ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bitfence Risk Oracle analyze_token ~/.cursor/mcp.json
- VS Code bitfence Risk Oracle analyze_token .vscode/mcp.json
- Zed bitfence Risk Oracle analyze_token ~/.config/zed/settings.json
- Windsurf bitfence Risk Oracle analyze_token ~/.codeium/windsurf/mcp_config.json
- Cline bitfence Risk Oracle analyze_token ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bitfence Risk Oracle analyze_token ~/.gemini/settings.json
- Grok bitfence Risk Oracle analyze_token .mcp.json (in your project root)
- ChatGPT bitfence Risk Oracle analyze_token Settings → Connectors → Advanced → Developer mode
- Claude.ai bitfence Risk Oracle analyze_token Settings → Connectors → Add custom connector
- LangChain bitfence Risk Oracle analyze_token pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bitfence https://api.bitfence.ai/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.