io.github.toolhail/gateway
Find and call the right MCP server for any task - pay per use, no install.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http gateway 'https://mcp.toolhail.com/mcp'{
"mcpServers": {
"gateway": {
"type": "http",
"url": "https://mcp.toolhail.com/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
ToolHail
The discovery-and-payment layer for AI agents. ToolHail lets an AI agent find the right MCP (Model Context Protocol) server for any task and call it — paying per use — without installing anything.
There are 10,000+ MCP servers an agent could use, and no good way to discover and use one mid-task. ToolHail closes that gap with two tools:
- 🔎
find_mcp_server(free) — describe a capability in plain language ("query a Postgres database","send a Slack message","scrape a web page") and get ranked, deduplicated MCP servers from every major registry (mcp.so, PulseMCP, Smithery, Glama) with ready-to-paste setup. - ⚡
call_tool(paid) — invoke a discovered remote MCP server through ToolHail's SSRF-guarded proxy. No install, one hop; each successful call is metered and billed through Stripe.
Use it
Hosted MCP endpoint (Streamable HTTP):
https://mcp.toolhail.com/mcpAdd it to Claude Code (or any MCP client):
claude mcp add --transport http toolhail https://mcp.toolhail.com/mcpMCP Scout on the Apify Store — the discovery engine as a standalone, pay-per-search actor: https://apify.com/01010101/mcp-scout
Site: https://toolhail.com · Guide: https://toolhail.com/guide
How it works
- Discover — the agent hits a capability gap and asks
find_mcp_server, which searches the registries and returns the best-fit servers, ranked for usability. - Execute — instead of installing, the agent calls the chosen tool via
call_tool; ToolHail proxies it in one hop, nothing to configure. - Settle — each successful call is metered and billed through Stripe. The agent pays for exactly what it used.
Why it exists
An agent's toolset is fixed at configuration time, but real tasks need capabilities the agent doesn't have. Today the options are "hard-code every server you might ever need" or "give up." ToolHail makes tools a runtime resource: discovered on demand, called through one endpoint, paid per use. It is discovery and payment infrastructure for the agentic web — built entirely on the open Model Context Protocol.
Repo layout
| Path | What |
|---|---|
apify-mcp-scout/ | MCP Scout — the discovery engine, published on the Apify Store (live) |
gateway-worker/ | Hosted MCP gateway on Cloudflare Workers — find_mcp_server + call_tool (live at mcp.toolhail.com) |
gateway/ | Reference gateway + Stripe metering + tests |
landing/ | toolhail.com site (landing + guide + llms.txt) |
registry/ | MCP registry listing metadata (server.json) + submission playbook |
dashboard/ | Private revenue/usage dashboard |
brand/ | Brand assets |
Built on
Model Context Protocol · Cloudflare Workers · Stripe · Apify
Frequently asked questions
What is io.github.toolhail/gateway?
Find and call the right MCP server for any task - pay per use, no install.
How do I install io.github.toolhail/gateway?
It runs as a remote server. In Claude Code: claude mcp add --transport http gateway 'https://mcp.toolhail.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.toolhail/gateway need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.toolhail/gateway open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.toolhail/gateway?
It is published by toolhail. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.