route_task — MCP Verify MCP Tool
route_task
(route task) is one of 22 tools on the
MCP Verify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call route_task from your client
- Claude Code MCP Verify route_task run in your project directory
- Claude Desktop MCP Verify route_task ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MCP Verify route_task ~/.cursor/mcp.json
- VS Code MCP Verify route_task .vscode/mcp.json
- Zed MCP Verify route_task ~/.config/zed/settings.json
- Windsurf MCP Verify route_task ~/.codeium/windsurf/mcp_config.json
- Cline MCP Verify route_task ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MCP Verify route_task ~/.gemini/settings.json
- Grok MCP Verify route_task .mcp.json (in your project root)
- ChatGPT MCP Verify route_task Settings → Connectors → Advanced → Developer mode
- Claude.ai MCP Verify route_task Settings → Connectors → Add custom connector
- LangChain MCP Verify route_task pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verify https://verify.sentinelsignal.io/mcpOther tools on this server
- search
- fetch
- search_servers
- recommend_servers
- get_server_report
- compare_servers
- decide_agent_call
- create_mandate
- get_evidence_pack
- compile_docs
- export_policy
- get_subscription_options
- get_gateway_options
- get_hosting_options
- list_agents
- get_agent
- score_agent
- explain_agent_risk
- list_high_risk_agents
- get_drift_report
- generate_remediation_plan
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.