# gateway

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/toolhail/toolbroker  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/gateway-4

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

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "gateway": {
    "command": "npx",
    "args": ["-y","gateway-4"]
  }
}
```

## Documentation & README

# ToolHail

**The discovery-and-payment layer for AI agents.** ToolHail lets an AI agent find the right [MCP](https://modelcontextprotocol.io) (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

| Path | What |
|------|------|
| [`apify-mcp-scout/`](https://github.com/toolhail/toolbroker/blob/HEAD/apify-mcp-scout/) | MCP Scout — the discovery engine, published on the Apify Store (**live**) |
| [`gateway-worker/`](https://github.com/toolhail/toolbroker/blob/HEAD/gateway-worker/) | Hosted MCP gateway on Cloudflare Workers — `find_mcp_server` + `call_tool` (**live** at `mcp.toolhail.com`) |
| [`gateway/`](https://github.com/toolhail/toolbroker/blob/HEAD/gateway/) | Reference gateway + Stripe metering + tests |
| [`landing/`](https://github.com/toolhail/toolbroker/blob/HEAD/landing/) | `toolhail.com` site (landing + guide + `llms.txt`) |
| [`registry/`](https://github.com/toolhail/toolbroker/blob/HEAD/registry/) | MCP registry listing metadata (`server.json`) + submission playbook |
| [`dashboard/`](https://github.com/toolhail/toolbroker/blob/HEAD/dashboard/) | Private revenue/usage dashboard |
| [`brand/`](https://github.com/toolhail/toolbroker/blob/HEAD/brand/) | Brand assets |

## Built on

Model Context Protocol · Cloudflare Workers · Stripe · Apify