Gateway

io.github.toolhailPublished by GitHub account toolhailv0.2.0Updated Oct 24, 2026

Find and call the right MCP server for any task - pay per use, no install.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

A hosted MCP gateway that lets an assistant search registries for a suitable MCP server and call it through a proxy, paying per use instead of installing.

What you can do
Search MCP registries by plain-language capability description and get ranked, deduplicated servers with setup details (free).
When to use it
Useful when a task needs a capability the assistant's fixed toolset lacks and you would rather discover and call a remote server on demand than install and configure one.
Requirements
A remote Streamable HTTP endpoint at mcp.toolhail.com added to an MCP client; no local runtime, packages, environment variables or headers are declared. Paid calls are billed through Stripe, so a payment arrangement is implied.
Before you install
The call tool is paid: each successful call is metered and billed through Stripe, so usage spends money. Calls are proxied through ToolHail to third-party remote servers, so request data passes through an intermediary and to the chosen server. The manifest declares no authentication, so check how billing and identity are tied to your account before use.

Installation

In SourceWeft

  1. Open Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.toolhail%2Fgateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://mcp.toolhail.com/mcp"
    }
  }
}

README

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/mcp

Add it to Claude Code (or any MCP client):

bash
claude mcp add --transport http toolhail https://mcp.toolhail.com/mcp

MCP 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

  1. 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.
  2. Execute — instead of installing, the agent calls the chosen tool via call_tool; ToolHail proxies it in one hop, nothing to configure.
  3. 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

PathWhat
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

Source: README.md at commit 287a891

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.