MCP QUEEN
io.github.seekdaseek/agentfeed A
Liquidation cascades across ~600 perps on 3 exchanges. Pay per call in USDC via x402.
Dev & Codev1.4.0streamable-httpx402.ochinimus.app repository
Grade evidence — probed 2026-07-14 20:00 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 124ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo agentfeed@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 18 tools e.g. "get_sol_price"; 18/18 described, 18/18 fully-typed schemas, median description 158 chars |
| latency | 10 / 10 | initialize round-trip 124ms |
| provenance | 15 / 15 | description present; repository linked; version 1.4.0; namespace io.github.seekdaseek matches endpoint/repo |
Score 100/100 · latency 124ms · 18 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http agentfeed https://x402.ochinimus.app/mcp
Generic MCP client config:
{ "mcpServers": { "agentfeed": { "type": "http", "url": "https://x402.ochinimus.app/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.seekdaseek/agentfeed · referral link https://mcpqueen.com/go/io.github.seekdaseek/agentfeed (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.seekdaseek/agentfeed)
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.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-14 20:00 | A | 100 | 124ms |