Back to Browse

Fetcher Cloud MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.

About

The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.

Remote endpoints: streamable-http: https://api.fetcher.cloud/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

19 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "cloud-fetcher-fetcher": {
      "url": "https://api.fetcher.cloud/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

fetcher.cloud — the web capability layer for AI agents

One MCP server and API that gives an autonomous AI agent the public web. Render and screenshot pages, extract clean content, resolve links, parse feeds, and inspect domains, DNS, SSL, and WHOIS — 18 capabilities, paid per-call in USDC via x402, with a free daily tier.

Whenever an agent needs something from the internet, it uses fetcher.

x402 MCP Cloudflare Workers License: MIT

Why it exists

LLMs are brilliant at reasoning and blind at retrieval. The moment real-world data needs a browser, a payment, or a login, an agent stalls. fetcher is the specialist capability layer it calls — a single interface for everything an agent can't do alone, billed the only way that works for software: per call, in stablecoins, with no account or API key.

How agents use it

  1. DiscoverGET /capabilities returns every capability with category, pricing, examples, and schemas. Or connect the MCP server at /mcp.
  2. Call — a normal GET request. The first unpaid call past the free tier returns 402 Payment Required with machine-readable terms.
  3. Pay — the agent's wallet pays a fraction of a cent in USDC on Base and retries. No human in the loop.

Works with Conway Automaton, Claude, OpenAI Agents, Google ADK, any MCP client, or any agent that can make an HTTP request.

The capabilities

CategoryCapabilities
Browser & renderingrender, screenshot
Content & extractionextract, unfurl, feed, oembed, pdf-text, diff
Web intelligenceresolve, headers, robots, favicon
Domain & DNSdomain, domain/enriched, whois, dns, ssl
Utilityqr

Full catalog with pricing and examples: https://api.fetcher.cloud/capabilities

Machine-readable surfaces

/ (manifest) · /capabilities · /pricing.json · /openapi.json · /mcp · /.well-known/ai-plugin.json · llms.txt

Repository layout

worker/         # the Cloudflare Worker (API, payments, MCP)   → see worker/README.md
website/        # the landing page (Cloudflare Pages)
test-client/    # a script that pays an endpoint on Base mainnet
conway-skill/   # ready-to-submit Conway Automaton skill

Deploy

See worker/README.md and DEPLOY.md for step-by-step deployment (Cloudflare Workers + Pages). Payments require Coinbase CDP facilitator keys set as Worker secrets.

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!