mcp server
SteadyFetch
Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass
Description as published by the maintainer. Source
- version 0.1.1
- slowing
slowing — Registry entry last updated 2026-03-31.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
cache_stats- Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.
check_domain(domain)- 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') Required: domain.
clear_cache- Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.
fetch_markdown(url, wait_for, use_cache)- 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 Required: url.
fetch_url(url, wait_for, js_render, use_cache)- 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') Required: url.
Last successful function declaration observed on . Source: https://steadyfetch-production.up.railway.app/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://steadyfetch-production.up.railway.app/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | steadyfetch-production.up.railway.app | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | steadyfetch-production.up.railway.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json