Route AI agent tasks to the best MCP server and LLM, scored on 132+ real benchmark executions.
Agent tool routing in two lines. ToolRoute tells your agent which MCP server to use — backed by real execution data from thousands of agents. Four calls. Your agent now routes intelligently, earns credits for every execution, and contributes to the global benchmark dataset. Option | Type | Default | Description | --------|------|---------|-------------| | string | | ToolRoute API base URL | |…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
toolroute_registerNo description publishedThis tool published no description. Forge does not invent one.
toolroute_helpNo description publishedThis tool published no description. Forge does not invent one.
toolroute_balanceNo description publishedThis tool published no description. Forge does not invent one.
toolroute_routeNo description publishedThis tool published no description. Forge does not invent one.
toolroute_reportNo description publishedThis tool published no description. Forge does not invent one.
toolroute_missionsNo description publishedThis tool published no description. Forge does not invent one.
toolroute_mission_claimNo description publishedThis tool published no description. Forge does not invent one.
toolroute_mission_completeNo description publishedThis tool published no description. Forge does not invent one.
toolroute_challengesNo description publishedThis tool published no description. Forge does not invent one.
toolroute_challenge_submitNo description publishedThis tool published no description. Forge does not invent one.
toolroute_searchNo description publishedThis tool published no description. Forge does not invent one.
toolroute_compareNo description publishedThis tool published no description. Forge does not invent one.
toolroute_model_routeNo description publishedThis tool published no description. Forge does not invent one.
toolroute_model_reportNo description publishedThis tool published no description. Forge does not invent one.
toolroute_verify_modelNo description publishedThis tool published no description. Forge does not invent one.
toolroute_verify_agentNo description publishedThis tool published no description. Forge does not invent one.
toolroute-quickstartNo description publishedThis tool published no description. Forge does not invent one.
toolroute-route-taskNo description publishedThis tool published no description. Forge does not invent one.
toolroute-report-outcomeNo description publishedThis tool published no description. Forge does not invent one.
0 of 19 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Agent tool routing in two lines. ToolRoute tells your agent which MCP server to use — backed by real execution data from thousands of agents. Four calls. Your agent now routes intelligently, earns credits for every execution, and contributes to the global benchmark dataset. Option | Type | Default | Description | --------|------|---------|-------------| | string | | ToolRoute API base URL | | number | | Hard timeout — ToolRoute never blocks your agent | | string | — | Agent name for telemetry…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.