mcpbeat

Gateway MCP Server

io.github.toolhail/gateway
answering

Gateway is answering right now. Last checked 10 min ago. It exposes 2 tools. Last commit 26 Jul 2026.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
938 ms
Response time
average over 24h
0
Stars
last commit 26 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add gateway --transport http https://mcp.toolhail.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://mcp.toolhail.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gateway]
url = "https://mcp.toolhail.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://mcp.toolhail.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://mcp.toolhail.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

call
call_tool
Proxy one tool call to a discovered remote MCP server (paid). Every call passes pre-execution guards before anything runs: tools on TOOLHAIL_BLOCKED_TOOLS are always refused; when TOOLHAIL_ALLOWED_TOOLS is set (non-empty, no "*") only listed tools may fire; write/mutating-looking tool names are refused unless allowWrite:true is passed or the tool is allowlisted; and TOOLHAIL_ARG_LIMITS can cap specific argument values per tool (e.g. daily_budget<=500) so an allowlisted broad tool still cannot push a value past its ceiling. Any refusal executes nothing and bills nothing, and every receipt records the gate decision.
mcp
find_mcp_server
no description provided

Endpoints

URLTransportStateLatencyChecked
https://mcp.toolhail.com/mcp streamable-http answering 837 ms 10 min ago

Gateway — questions

Answers built from our own checks of this server.

What can Gateway do?
It exposes 2 tools, read directly from the server on our last check. Among them: call_tool, find_mcp_server. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Gateway working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 938 ms. The bar chart above shows every period we have measured.
How do I connect Gateway?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Gateway need an API key?
No. Gateway completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Gateway?
It answers our handshake in 938 ms on average, which is faster than 6% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Gateway open source?
Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.