Skip to content
Fetcher logo

Fetcher MCP server

Which MCP servers are Fetcher's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-23

← Back to Fetcher

Whose server it is
  • Registry namecloud.fetcher/fetcherverified in the MCP registry

The registry name sits under fetcher.cloud. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-23
  • Stateanswerschecked 2026-10-23
  • Tools19
  • Server calls itselffetcher.cloud
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 395 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: render JavaScript-only pages so an agent can read them; resolve shortened or tracking links to their final destination; check live domain availability across TLDs via RDAP.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "render JavaScript-only pages so an agent can read them", the likely first call is render_page.
  • For "resolve shortened or tracking links to their final destination", the likely first call is resolve_url.
  • For "check live domain availability across TLDs via RDAP", the likely first call is check_domain.
  • Parameters are untyped or undescribed in 11 of 19 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-23
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer206 ms
  • Space in an agent's context≈ 1,596 tokensthe definitions of all its tools (19), which an agent carries on every turn
  • Tool definitionsC · 74 of 100
  • Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 11 of 19
  • Not saying whether it only reads or can destroy: 19 of 19

What an agent can do with it

  • can do · render JavaScript-only pages so an agent can read them
  • can do · resolve shortened or tracking links to their final destination
  • can do · check live domain availability across TLDs via RDAP

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers19 tools · read 2026-10-23
  • render_page

    Render a JavaScript page in a real browser; returns rendered HTML, text, optional screenshot. (browser; $0.02/call in USDC via x402, 10 free/day).

  • screenshot_page

    Screenshot a page (real browser) as a base64 PNG/JPEG. (browser; $0.02/call in USDC via x402, 10 free/day).

  • extract_content

    Extract a page's main content as clean Markdown + text with metadata. (content; $0.005/call in USDC via x402, 30 free/day).

  • resolve_url

    Follow a URL's full redirect chain; return final URL, hops, and metadata. (web-intel; $0.003/call in USDC via x402, 50 free/day).

  • unfurl_url

    Link preview card (title, description, image, favicon) for any URL. (content; $0.003/call in USDC via x402, 50 free/day).

  • get_feed

    Discover and parse a site's RSS/Atom feed into JSON items. (content; $0.003/call in USDC via x402, 40 free/day).

  • get_oembed

    Rich embed (oEmbed) data for a media URL (YouTube, Vimeo, X, Spotify...). (content; $0.002/call in USDC via x402, 50 free/day).

  • find_favicon

    Find a site's best icon/logo. (web-intel; $0.002/call in USDC via x402, 50 free/day).

  • check_robots

    Parse robots.txt; answer whether a user-agent may crawl a path; list sitemaps. (web-intel; $0.002/call in USDC via x402, 50 free/day).

  • inspect_headers

    HTTP response headers + security-header analysis for a URL. (web-intel; $0.002/call in USDC via x402, 50 free/day).

  • dns_lookup

    Full DNS record dump (A/AAAA/MX/NS/TXT/SOA/CAA/CNAME) for a host. (domain-dns; $0.003/call in USDC via x402, 50 free/day).

  • ssl_lookup

    TLS certificate details (issuer, expiry, SANs) via Certificate Transparency logs. (domain-dns; $0.004/call in USDC via x402, 40 free/day).

  • whois_lookup

    Deep domain registration record via RDAP (registrar, dates, nameservers, DNSSEC). (domain-dns; $0.005/call in USDC via x402, 40 free/day).

  • extract_pdf

    Extract text + metadata from a PDF URL (text-based PDFs). (content; $0.01/call in USDC via x402, 20 free/day).

  • generate_qr

    Generate a QR code (SVG) for text or a URL. (utility; $0.002/call in USDC via x402, 50 free/day).

  • diff_pages

    Compare two pages (or one page vs its latest Wayback snapshot); return what changed. (content; $0.008/call in USDC via x402, 25 free/day).

  • guard_inspect

    Screen untrusted content (web pages, emails, tool output) for prompt-injection/manipulation before your agent trusts it. Returns a risk score + reasons; a screening signal, not a guarantee. (security; $0.005/call in USDC via x402, 30…

  • guard_tx

    Pre-sign wallet firewall: decode a transaction and flag unlimited approvals, setApprovalForAll, scam addresses, and spend-cap breaches before signing. Returns a risk verdict + reasons. (security; $0.008/call in USDC via x402, 25 free/day).

  • check_domain

    Check domain availability across TLDs via RDAP. Set enriched=true for DNS, age, and Wayback history. (domain-dns; $0.004/call in USDC via x402, 50 free/day).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "fetcher": {
      "type": "http",
      "url": "https://api.fetcher.cloud/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http fetcher https://api.fetcher.cloud/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.fetcher.cloud/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.