Accesses public-web content, rendering, extraction, domain, DNS, SSL, WHOIS, and utility capabilities through MCP and x402.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Fetcher.
The fetcher MCP server gives AI agents a single interface for public-web retrieval and inspection. It covers browser-oriented tasks such as rendering a page or taking a screenshot, content tasks such as extracting readable material and parsing feeds, and web utility tasks such as resolving links or retrieving headers.
It also exposes domain and network information. Available capabilities include domain lookup, enriched domain lookup, WHOIS, DNS, SSL, robots data, favicons, oEmbed data, PDF text extraction, QR generation, and page diffs. The catalog is published at https://api.fetcher.cloud/capabilities, where each capability includes pricing, examples, and schemas.
The fetcher MCP server is available through streamable HTTP at /mcp. Agents can also inspect the service through machine-readable endpoints including /, /capabilities, /pricing.json, /openapi.json, /.well-known/ai-plugin.json, and llms.txt.
A client discovers available operations, then sends a normal request for the selected capability. Requests within the free daily allowance can run without payment. After that allowance is exceeded, the service returns HTTP 402 Payment Required with machine-readable payment terms. An agent wallet can pay the requested amount in USDC on Base through x402 and retry the request. This design supports agents that can handle HTTP and payment flows without requiring an account or API key.
For hosted use, connect an MCP client to the service's /mcp endpoint. The repository also contains a Cloudflare Worker implementation, a website deployment, a payment test client, and a Conway Automaton skill. Deployment instructions are provided in the repository's worker/README.md and DEPLOY.md files.
A self-managed deployment runs on Cloudflare Workers and Pages. Payment processing requires Coinbase CDP facilitator keys configured as Worker secrets. The provided material does not specify the secret names or a local environment-variable configuration.
The fetcher MCP server groups its operations into these areas:
render, screenshotextract, unfurl, feed, oembed, pdf-text, diffresolve, headers, robots, favicondomain, domain/enriched, whois, dns, sslqrUse the capability catalog or OpenAPI document for the current schemas, examples, and prices rather than assuming all operations accept the same inputs.
The service is focused on the public web. Paid usage is metered per call in USDC through x402, although a free daily tier is available. Agents or clients must support the MCP connection and, for usage beyond the free allowance, the required payment flow. The README names Conway Automaton, Claude, OpenAI Agents, Google ADK, and general MCP or HTTP-capable agents as supported usage contexts; it does not document client-specific setup details.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/fetcher-2)<a href="https://allmcps.com/mcp/fetcher-2"><img src="https://allmcps.com/api/badge/fetcher-2?style=directory" alt="Fetcher on AllMCPs" /></a>