Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass
Dev & Codev0.1.1streamable-httpsteadyfetch-production.up.railway.app
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 121ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo steadyfetch@1.27.0 |
| tooling | 35 / 35 | tools/list OK: 5 tools e.g. "fetch_url"; 5/5 described, 5/5 fully-typed schemas, median description 307 chars |
| latency | 10 / 10 | initialize round-trip 121ms |
| provenance | 5 / 15 | description present; no repository URL; version 0.1.1; namespace io.github.carsonroell-debug does NOT match remote host (expected *.carsonroell-debug.github.io) |
Score 90/100 · latency 121ms · 5 tools · auth: open
Claude Code:
claude mcp add --transport http steadyfetch https://steadyfetch-production.up.railway.app/mcp
Generic MCP client config:
{ "mcpServers": { "steadyfetch": { "type": "http", "url": "https://steadyfetch-production.up.railway.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.carsonroell-debug/steadyfetch · referral link https://mcpqueen.com/go/io.github.carsonroell-debug/steadyfetch (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.carsonroell-debug/steadyfetch)
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 22:30 | A | 90 | 121ms |