MCP server for HyperRoute — routes each task to the best external tool and runs it for your coordinator agent.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"hyperroute-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# hyperroute-mcp The official [Model Context Protocol](https://modelcontextprotocol.io) server for **[HyperRoute](https://hyperroute.io)**. HyperRoute is a router for AI agents. Give it a task and it picks the best external tool for *that* task — measured, not advertised — then runs the tool for you with your own key held server-side, and learns from how it went. This MCP server is how a coordinator agent (Claude Code, Codex, Goose, Cursor, LangGraph, …) drives it: > recommend → onboard a key → execute the tool server-side → report the outcome It talks to the router only over its public HTTP API and holds no product logic of its own. ## Why route at all An agent with 100 tools bolted on has a context problem and a quality problem. HyperRoute replaces both with one verb: your agent learns `recommend`, and HyperRoute decides which of hundreds of tools actually answers this task, whether you can already do it better yourself, and what it will cost. - **Measured, not advertised.** Every capability score is backed by real graded probes you can inspect (`describe(tool_id, ["evidence"])`). - **Your keys never leave the server.** You connect a key once; HyperRoute runs the tool with it and returns only the result. The key is never sent to your agent, never logged. - **It tells you when NOT to route.** If nothing beats what your coordinator already does, the verdict is `use_native` — do it yourself. That only works if the server knows which coordinator it runs inside; see [Declaring your coordinator](#declaring-your-coordinator). ## Install ```bash pip install hyperroute-mcp ``` Or with [`pipx`](https://pipx.pypa.io), so the command is always on your PATH regardless of which virtualenv is active — which is what MCP clients need, since they launch the server themselves: ```bash pipx install hyperroute-mcp ``` From source, for development: ```bash git clone https://github.com/HyperRouteAI/hyperroute-mcp cd hyperroute-mcp python -m venv .venv && source .ve…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.