Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.
Otherv2.0.3streamable-httpapi.metamesh-uga.dev repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 120ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo metamesh-uga-gateway@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 17 tools e.g. "metamesh.context"; 17/17 described, 17/17 fully-typed schemas, median description 180 chars |
| latency | 10 / 10 | initialize round-trip 120ms |
| provenance | 15 / 15 | description present; repository linked; version 2.0.3; namespace dev.metamesh-uga matches endpoint/repo |
Score 100/100 · latency 120ms · 17 tools · auth: open
Claude Code:
claude mcp add --transport http metamesh-uga https://api.metamesh-uga.dev/mcp
Generic MCP client config:
{ "mcpServers": { "metamesh-uga": { "type": "http", "url": "https://api.metamesh-uga.dev/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/dev.metamesh-uga/metamesh-uga · referral link https://mcpqueen.com/go/dev.metamesh-uga/metamesh-uga (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/dev.metamesh-uga/metamesh-uga)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 10:30 | A | 100 | 120ms |