MCP Aggregation Gateway — 22k+ MCP search & call
REMOTE · MCP.PIANAM.CN
One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key.
Available components
Last scanned (41 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Sep 2026.
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Sept 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.pianam.cn/ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.pianam.cn. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.pianam.cn. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pianam.cn/ai/mcp | Unreachable | ||
| http (plaintext) | http://mcp.pianam.cn/ai/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_server_tool ~237
通过网关代理调用某个远程 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 标识是否业务错误）。
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | – |
| endpoint | string | yes | – |
| tool_name | string | yes | – |
No output schema declared.
No examples provided.
list_server_tools ~240
列出某个远程 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=...) 调用。
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | – |
| server_id | integer | – | – |
No output schema declared.
No examples provided.
search_servers ~352
搜索 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)且有远程端点的优先，其次按名称相关度。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the MCP Aggregation Gateway — 22k+ MCP search & call server?
MCP Aggregation Gateway — 22k+ MCP search & call is a hosted endpoint at https://mcp.pianam.cn/ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.pianam.cn
claude mcp add --transport http cn-pianam-mcp-mcp-gateway 'https://mcp.pianam.cn/ai/mcp'
What is the MCP Aggregation Gateway — 22k+ MCP search & call server?
MCP Aggregation Gateway — 22k+ MCP search & call is listed in the public MCP registry as cn.pianam.mcp/mcp-gateway. One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key. This page covers its hosted endpoint (https://mcp.pianam.cn/ai/mcp).
Is the MCP Aggregation Gateway — 22k+ MCP search & call server safe to use?
MCP Aggregation Gateway — 22k+ MCP search & call scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Aggregation Gateway — 22k+ MCP search & call server expose?
MCP Aggregation Gateway — 22k+ MCP search & call exposes 3 tools: search_servers, list_server_tools, call_server_tool. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.
Does the MCP Aggregation Gateway — 22k+ MCP search & call server require authentication?
Its publisher declares no required credentials for MCP Aggregation Gateway — 22k+ MCP search & call. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MCP Aggregation Gateway — 22k+ MCP search & call server still maintained?
MCP Aggregation Gateway — 22k+ MCP search & call has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.