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