SteadyFetch MCP server

• cache_statsFree

  Get cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.

• check_domainFree

  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')

• clear_cacheFree

  Clear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.

• fetch_markdownFree

  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

• fetch_urlFree

  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')

• Code scan8 source files scanned25/25
• Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"status":"error","code":404,"message":"Application not found","request_id":"eN7LRDA0TFK4H8_uwUFZXw"}0/20
• –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Safety score

49/100

higher than 9% of 48,255 servers

Tools

5

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

0%

of our recent checks; the typical remote server answers 100%

Response time

93 ms

faster than 86% of 30,031 servers

Downloads a week

17

more than 5% of 12,191 servers with a package

Grade history

• 2026-10-14downgradeB → Dscore 49: Remote endpoint did not respond; No source repository listed

SteadyFetch: common questions

Is SteadyFetch MCP server safe?

Not recommended: it is graded D (49/100). Read the SteadyFetch safety report

How do I install SteadyFetch?

It runs remotely at steadyfetch-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does SteadyFetch need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is SteadyFetch maintained?

The latest release is v0.1.1.

Is SteadyFetch up?

0% of our last 28 checks got an answer. We check remote servers about four times a day.

How does SteadyFetch compare with other MCP servers?

safety score 49/100 (higher than 9% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.