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