Size-aware exit cost, depeg risk & liquidity fragility for a Base token (x402, testnet).
Dev & Codev0.1.0streamable-httpagentdata-liquidity-exit-cost.onrender.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 525ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo agentdata-liquidity@1.28.0 |
| tooling | 35 / 35 | tools/list OK: 1 tools e.g. "liquidity_exit_cost"; 1/1 described, 1/1 fully-typed schemas, median description 789 chars |
| latency | 7 / 10 | initialize round-trip 525ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.0; namespace io.github.phenicea matches endpoint/repo |
Score 97/100 · latency 525ms · 1 tools · auth: open
Claude Code:
claude mcp add --transport http agentdata-liquidity-exit-cost https://agentdata-liquidity-exit-cost.onrender.com/mcp/
Generic MCP client config:
{ "mcpServers": { "agentdata-liquidity-exit-cost": { "type": "http", "url": "https://agentdata-liquidity-exit-cost.onrender.com/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.phenicea/agentdata-liquidity-exit-cost · referral link https://mcpqueen.com/go/io.github.phenicea/agentdata-liquidity-exit-cost (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.phenicea/agentdata-liquidity-exit-cost)
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 08:31 | A | 97 | 525ms |