Other · Remote MCP server
ToolBudget Router MCP
Paid remote MCP for context-budget routing, schema cost estimates, usage audits, and readiness.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.clauxel.toolbudgetrouter/toolbudgetrouter-mcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-05-17
- Updated
- 2026-05-17
- Publisher
- com.clauxel.toolbudgetrouter
- Namespace
- Namespace verified by the MCP Registry via the domain toolbudgetrouter.clauxel.com or a parent domain of it · how
- Website
- toolbudgetrouter.clauxel.com/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://toolbudgetrouter.clauxel.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
How to connect ToolBudget Router MCP
ToolBudget Router MCP is a remote MCP server: there is nothing to install. Its endpoint is https://toolbudgetrouter.clauxel.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, toolbudgetrouter.clauxel.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| TookEffectIndependent effect verification and signed receipts for consequential AI agent actions. | Remote · HTTPLive check: sign-in required |
| Tool Poisoning ScannerScans MCP tool definitions for hidden instructions and confused-deputy sinks. | Local · stdio |
| Toolalize MCPFree unit & live currency conversion tools from toolalize.com (convert_units, convert_currency). | Remote · HTTPLive check: ✓ handshake |
| ToolAPIFree public MCP for AI agents - 193 tools, 44 workflows. No API key. | Remote · SSE, HTTPLive check: ✓ handshake |
| Toolcairn MCPMCP server for tool discovery: find, compare, and verify tools across 35+ registries. | Local · stdio |
| Toolchain Lens MCPLocal explanation of reproducibility signals and toolchain contradictions without exact versions... | Local · stdio |
| ToolfactoryBuild an agent tool once; ship it as Agent Skills, MCP servers, Agent Plugins / Claude / Codex. | Local · stdio |
| ToolforestHosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc. | Remote · HTTPLive check: sign-in required |