MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents
Dev & Codev1.7.0streamable-httpmcp.x402layer.cc
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 184ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo singularity-mcp@1.8.0 |
| tooling | 33 / 35 | tools/list OK: 38 tools e.g. "browse_marketplace"; 38/38 described, 30/38 fully-typed schemas, median description 134 chars |
| latency | 10 / 10 | initialize round-trip 184ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.7.0; namespace io.github.ivaavimusic does NOT match remote host (expected *.ivaavimusic.github.io) |
Score 88/100 · latency 184ms · 38 tools · auth: open
Claude Code:
claude mcp add --transport http singularity https://mcp.x402layer.cc/mcp
Generic MCP client config:
{ "mcpServers": { "singularity": { "type": "http", "url": "https://mcp.x402layer.cc/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/io.github.ivaavimusic/singularity · referral link https://mcpqueen.com/go/io.github.ivaavimusic/singularity (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.ivaavimusic/singularity)
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-14 02:45 | B | 88 | 184ms |