Koskamo

ToolRoute MCP

ToolRoute allows AI agents to register a list of tools or a remote MCP server once, then sends a task to receive the 3-12 most relevant tools for that prompt using deterministic keyword ranking without LLMs. This helps agents manage context windows by selecting only necessary tools from a large registry.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

ToolRoute MCP logo, by YourAIToolsVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by YourAITools
MCP endpoint (Streamable HTTP)
https://api.youraitools.co/toolroute/mcp
Vendor documentation

What you can do with it

  • Register a tool list or remote MCP server once
  • Route agent tasks to the 3-12 most fitting tools
  • Inject selected tools for OpenAI, Anthropic, Gemini or MCP

Source and maintenance

Vendor evidenceRegistry 0.1.1

Protocol and capabilities

Server
toolroute 0.1.0
MCP protocol
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

ToolRoute narrows a large tool list to the few tools a task needs. Call register_tools once with your tools (or a remote MCP URL) to get a set_id, then route_tools with set_id + the task for each turn and inject only the returned definitions. BM25 keyword ranking, no LLM. Free: 200 route_tools calls per IP per day; register_tools is free.

Tools

2 advertised

register_tools — Register a tool set (ToolRoute)
Advertised by the server during the last successful anonymous check.
Open-world

Register a tool list once and get a set_id for route_tools. Pass "tools" (array in MCP, OpenAI, Anthropic, Gemini or Bedrock form, max 500) or "url" (public remote MCP server; its tools are listed, never called). Same tools always get the same set_id; sets are kept 90 days after last use. Free.

register_tools input schema
{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Register: public remote MCP server URL (https). Tools are listed, never called."
    },
    "tools": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Tool definitions (MCP, OpenAI, Anthropic, Gemini or Bedrock form), max 500. For route: only if you have no set_id (the set is registered on the fly)."
    }
  }
}
register_tools annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": true
}
route_tools — Route a task to the right tools (ToolRoute)
Advertised by the server during the last successful anonymous check.
Advertised read-only

Which of my tools does this task need? Send "set_id" (from register_tools) or "tools", plus "query" (the task). Returns a ranked shortlist (adaptive 3-12 tools, or "k"), confidence (high/medium/low/none), matched terms, token savings and the definitions ready to inject ("format": mcp, openai, anthropic, gemini or names). BM25 keyword ranking, no LLM. Free: 200 calls/day per IP, then $0.001 per call via x402 or credits.

route_tools input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "k": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Fixed shortlist size (default adaptive)"
    },
    "max_k": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Upper bound for the adaptive size (default 12)"
    },
    "query": {
      "type": "string",
      "description": "The task or user request to route, e.g. \"check if this wallet is sanctioned\"."
    },
    "tools": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Tool definitions (MCP, OpenAI, Anthropic, Gemini or Bedrock form), max 500. For route: only if you have no set_id (the set is registered on the fly)."
    },
    "format": {
      "enum": [
        "mcp",
        "openai",
        "anthropic",
        "gemini",
        "names"
      ],
      "type": "string",
      "description": "Definition format (default mcp; names = names only)"
    },
    "set_id": {
      "type": "string",
      "description": "set_id (\"ts_...\" from register, or a ToolFit pin)."
    }
  }
}
route_tools annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
396 ms
95th percentile latency
396 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 396 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http toolroute-mcp https://api.youraitools.co/toolroute/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add toolroute-mcp --url https://api.youraitools.co/toolroute/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable toolroute-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "toolroute-mcp": {
      "url": "https://api.youraitools.co/toolroute/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "toolroute-mcp": {
      "type": "streamableHttp",
      "url": "https://api.youraitools.co/toolroute/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start toolroute-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "toolroute-mcp": {
      "type": "http",
      "url": "https://api.youraitools.co/toolroute/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http toolroute-mcp https://api.youraitools.co/toolroute/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "toolroute-mcp": {
      "url": "https://api.youraitools.co/toolroute/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "toolroute-mcp": {
      "serverUrl": "https://api.youraitools.co/toolroute/mcp"
    }
  }
}

Let your agent find its tools

Find servers like ToolRoute MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run ToolRoute MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing