✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.
What it offers — 5 tools · AI & ML
fetch_url
Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass. Returns both raw HTML and clean markdown. Automatically retrie
fetch_markdown
Fetch a URL and return clean markdown text optimized for LLM consumption. Same reliability as fetch_url but returns only the markdown content, strippi
check_domain
Check the health status of a domain. Returns the circuit breaker state: 'closed' (healthy), 'open' (failing), or 'half_open' (testing recovery). Use t
cache_stats
Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.
clear_cache
Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.
Spec conformance20%80
✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✗ unknown method → -32602
✓ tools/list → 5 tools
✓ every tool has name + inputSchema
Security (OWASP MCP)30%100
5 tools scanned
no injection markup
no secret-path refs
Reliability / performance20%92
single-probe latency 596ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)
Tool hygiene15%76
60% of tools have typed inputSchema
5/5 declare outputSchema
no unannotated destructive tools
Transparency / provenance15%70
HTTPS ✓
advertises protocol 2025-06-18
Observed behavior
No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.
Findings
No blocking issues found in the static + spec checks.
We re-grade steadyfetch-production.up.railway.app on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
<a href="https://wmcp.sh/mcp/grade/steadyfetch-production.up.railway.app"><img src="https://wmcp.sh/mcp/grade/steadyfetch-production.up.railway.app/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>
Agents: check this before connecting
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.