steadyfetch
https://steadyfetch-production.up.railway.app
Registry code: f45b0dfec36875b6
SteadyFetch provides reliable web fetching for AI agents. Use fetch_url to get any webpage with automatic retry, anti-bot bypass, circuit breaker protection, and caching. Use fetch_markdown for LLM-optimized clean text. Use check_domain to see if a site is currently reachable.
- endpoint
- https://steadyfetch-production.up.railway.app/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is steadyfetch live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is steadyfetch free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does steadyfetch have?
- 5 tools: check_domain, fetch_markdown, clear_cache, fetch_url, cache_stats.
- Is steadyfetch safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 5 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- search & web scraping & fetch
- used for
- fetch a webpage reliably
- get clean markdown of a url
- check domain reachability
- takes → gives
- web pages → text, web pages
- tools
- 4 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
cache_stats reads open 32d ago
Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.
{ "type": "object", "title": "cache_statsArguments", "properties": {} }arguments 5 linescheck_domain reads unknown 32d ago
Check the health status of a domain. Returns the circuit breaker state: 'closed' (healthy), 'open' (failing), or 'half_open' (testing recovery). Use this before batch operations to avoid wasting time on domains that are down. Args: domain: The domain to check (e.g., 'example.com')
{ "type": "object", "title": "check_domainArguments", "required": [ "domain" ], "properties": { "domain": { "type": "string", "title": "Domain" } } }arguments 13 linesfetch_markdown reads unknown 32d ago
Fetch a URL and return clean markdown text optimized for LLM consumption. Same reliability as fetch_url but returns only the markdown content, stripping HTML, scripts, and noise. Best for when you need the page content for analysis, summarization, or data extraction. Args: url: The URL to fetch use_cache: Whether to use cached results (default: true) wait_for: CSS selector to wait for before capturing
{ "type": "object", "title": "fetch_markdownArguments", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "Url" }, "wait_for": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Wait For", "default": null }, "use_cache": { "type": "boolean", "title": "Use Cache", "default": true } } }arguments 30 linesclear_cache changes data unknown never probed
Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.
{ "type": "object", "title": "clear_cacheArguments", "properties": {} }arguments 5 linesfetch_url reads unknown 32d ago
Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass. Returns both raw HTML and clean markdown. Automatically retries on failure with exponential backoff, falls back to plain HTTP if browser fetch fails, and circuit-breaks domains that are consistently down. Args: url: The URL to fetch use_cache: Whether to use cached results (default: true, TTL 1 hour) js_render: Whether to render JavaScript (default: true, disable for speed) wait_for: CSS selector to wait for before capturing (e.g., '.results-loaded')
{ "type": "object", "title": "fetch_urlArguments", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "Url" }, "wait_for": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Wait For", "default": null }, "js_render": { "type": "boolean", "title": "Js Render", "default": true }, "use_cache": { "type": "boolean", "title": "Use Cache", "default": true } } }arguments 35 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf45b0dfec36875b6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f45b0dfec36875b6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f45b0dfec36875b6?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.