mcpbeat Sign in

MCP Aggregation Gateway — 22k+ MCP search & call MCP Server

answering

MCP Aggregation Gateway — 22k+ MCP search & call is answering right now. Last checked 3 min ago. It exposes 3 tools.

One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key.

Uptime history 6 days of history · worst day 99%
6 days agonow
100.0%
Uptime 24h
93 of 93 checks
3
Tools
read from the server
1132 ms
Response time
average over 24h
open, no key
Access
streamable-http

MCP Aggregation Gateway — 22k+ MCP search & call does not always answer

Over the last week it answered 99.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

Available tools 3

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

call
call_server_tool
通过网关代理调用某个远程 MCP 服务的具体工具,并把结果原样返回。 【这是调用平台 MCP 的第三步】在 search_servers 找到服务、list_server_tools 拿到工具名与 入参 schema 后,调用本工具实际执行。网关会向目标 MCP 发起 initialize + tools/call(超时 30 秒), 兼容 Streamable HTTP 与 SSE。 参数: endpoint: 目标远程 MCP 端点 URL(必须是平台库中已登记的地址,否则拒绝,防 SSRF)。 tool_name: 要调用的工具名(来自 list_server_tools)。 arguments: 工具入参字典,按该工具 inputSchema 填写。例如 {"city": "青岛", "days": 3}。 返回:目标工具的执行结果(content 文本/结构化内容原样透传,isError 标识是否业务错误)。
server
list_server_tools
列出某个远程 MCP 服务提供的全部工具(工具名、描述、入参 schema)。 【这是调用平台 MCP 的第二步】在 search_servers 找到目标服务后,传入它的 server_id (或直接传 endpoint_url),网关会以 MCP 客户端身份向目标服务发起 initialize + tools/list, 兼容 Streamable HTTP 与旧版 SSE 两种传输(超时 15 秒)。 参数: server_id: 平台目录中的服务 ID(来自 search_servers 返回的 id)。 endpoint: 也可直接给远程 MCP 端点 URL;但该 endpoint 必须已在平台库中登记(否则拒绝,防 SSRF)。 二选一,优先使用 server_id。 返回:目标服务的工具清单 [{name, description, inputSchema}] 与使用的传输类型。 拿到工具名后,用 call_server_tool(endpoint=..., tool_name=..., arguments=...) 调用。
servers
search_servers
搜索 MCP Marketplace 平台目录中已收录的 MCP 服务(只读,共约 2.2 万个)。 【这是调用平台 MCP 的第一步】当你需要某个能力(如"查天气""查汇率""查热搜""查IP")时, 先用本工具按关键词检索,拿到 server_id 与 endpoint_url,然后: - 用 list_server_tools(server_id=...) 查看该服务提供哪些工具; - 再用 call_server_tool(endpoint=..., tool_name=..., arguments={...}) 实际调用。 参数: query: 搜索关键词,中英文均可。支持多个关键词(空格分隔,AND 匹配), 对名称(name)和描述(description)做模糊匹配。例如 "天气"、"weather"、"热搜 微博"。 limit: 返回条数上限,默认 10,最大 30。 返回:匹配的 MCP 列表,每条含: - id / name / slug / description(描述摘要) - endpoint_url: 远程 MCP 端点(若有;以 http/https 开头则 remote_direct=true,可直接远程调用) - remote_direct: 是否远程可直连 - alive / tools_count / checked_at: 平台能力验证状态(alive=1 表示最近验证存活,排在前面) 排序:验证存活(alive=1)且有远程端点的优先,其次按名称相关度。

Endpoints

URLTransportStateLatencyChecked
https://mcp.pianam.cn/ai/mcp streamable-http answering 1902 ms 3 min ago

Alternatives to MCP Aggregation Gateway — 22k+ MCP search & call

same job, measured the same way
GoModel
by enterpilot

Self-hosted gateway aggregating upstream MCP servers behind one authenticated HTTP endpoint.

local only
AISIX AI Gateway
by api7

Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint

local only
C
Enterprise MCP Gateway
by thenextgennexus

Unified gateway exposing 150+ tools across all NexGenData MCP servers via one endpoint.

152 tools answering
Manifold
by nonchan7720

MCP gateway aggregating MCP servers and OpenAPI/Swagger REST APIs behind one MCP endpoint

local only
Marketplace
by jojapi

Search the JoJ API marketplace, read endpoint docs, and call any API with one key via one gateway.

4 tools answering
Anythingmcp
by keysersoft

Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.

4 tools answering
treg.to
by superdesigndev

OpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.

answering
Chain.Love MCP
by chain-app

Hosted MCP gateway for Web3 infra discovery across 20+ networks via one endpoint.

5 tools answering

MCP Aggregation Gateway — 22k+ MCP search & call — questions

Answers built from our own checks of this server.

What can MCP Aggregation Gateway — 22k+ MCP search & call do?
It exposes 3 tools, read directly from the server on our last check. Among them: call_server_tool, list_server_tools, search_servers. 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 MCP Aggregation Gateway — 22k+ MCP search & call working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 1132 ms. The bar chart above shows every period we have measured.
How do I connect MCP Aggregation Gateway — 22k+ MCP search & call?
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 MCP Aggregation Gateway — 22k+ MCP search & call need an API key?
No. MCP Aggregation Gateway — 22k+ MCP search & call completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MCP Aggregation Gateway — 22k+ MCP search & call?
It answers our handshake in 1132 ms on average, which is faster than 5% 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.