Home / MCP registry index / io.github.Humanleap/toolrouter

ToolRouter

io.github.Humanleap/toolrouter in the official MCP registry. Endpoint https://api.toolrouter.com/mcp. Source: github.com/Humanleap/toolrouter-mcp.

The registry describes it as: The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.

We read its 48 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http toolrouter https://api.toolrouter.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "toolrouter": {
      "url": "https://api.toolrouter.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"toolrouter","type":"http","url":"https://api.toolrouter.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

account_setup account_list account_switch account_preferences credits_balance credits_usage subscription_manage invoice_list key_list key_create key_delete credential_list credential_save credential_delete credential_default credential_guide file_list file_read file_write file_delete persona_list scene_list product_list outfit_list connector_list connector_add connector_remove brain_admin job_list job_get job_cancel feedback_review feedback_debug feedback_request_tool top_up_credits discover route use_tool brain_query brain_add brain_update brain_delete brain_status brain_lint brain_settings brain_expand brain_wings connector_permissions

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-humanleap-toolrouter/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-humanleap-toolrouter)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.