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