SteadyFetch

Reliable web fetching MCP server with built-in retry logic, circuit breaker patterns, caching, and anti-bot bypass.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Fetch Url: 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,
  • 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, stripping HTML, scripts, and noise. Best
  • Check 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

What data it sees

Do you need an account

No: the server works without sign-in

Reliable web fetching MCP server with built-in retry logic, circuit breaker patterns, caching, and anti-bot bypass. Fetches URLs as raw HTML or clean markdown optimized for LLM consumption. Includes domain health checks and cache management tools.

How to connect

How to connect SteadyFetch to Claude

The server address to paste into Claude settings:

https://steadyfetch--intake-triage.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect SteadyFetch to ChatGPT

The server address to paste into ChatGPT settings:

https://steadyfetch--intake-triage.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect SteadyFetch to Cursor

The server address to paste into Cursor settings:

https://steadyfetch--intake-triage.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

fetch_urlFetch 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')
fetch_markdownFetch 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
check_domainCheck 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')
cache_statsGet cache statistics — size and item count. Useful for monitoring cache utilization and deciding when to clear.
clear_cacheClear the entire fetch cache. Use when you need fresh data and don't want to rely on cached results.