Developer · Remote MCP server
Fetcher
The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.fetcher/fetcher- Version
- 1.1.3
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-04
- Updated
- 2026-08-04
- Publisher
- cloud.fetcher
- Namespace
- Namespace verified by the MCP Registry via the domain fetcher.cloud · how
- Website
- fetcher.cloud
- Repository
- github.com/fetchercloud/fetcher-cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.fetcher.cloud/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- fetcher.cloud 1.1.0 · protocol 2025-06-18
- Tools discovered
19 - show names
render_page,screenshot_page,extract_content,resolve_url,unfurl_url,get_feed,get_oembed,find_favicon,check_robots,inspect_headers,dns_lookup,ssl_lookup,whois_lookup,extract_pdf,generate_qr,diff_pages,guard_inspect,guard_tx,check_domain- Checked on
- 2026-10-05
How to connect Fetcher
Fetcher is a remote MCP server: there is nothing to install. Its endpoint is https://api.fetcher.cloud/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Fenestra MCPRender and verify native Rust GUIs headlessly: access tree, query, a11y, screenshots, motion. | Local · stdio |
| Feode MCPFEODE: AI-accessible precision machining & testing; offshore P&A, subsea wellhead, drill-pipe. | Remote · HTTPLive check: ✓ handshake |
| Feranor ResilienceScan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions. | Remote · HTTPLive check: ✓ handshake |
| Ferritin - Rust documentationSearch and read Rust documentation for the standard library and any crate on crates.io. | Remote · HTTPLive check: ✓ handshake |
| FetchSandboxA deterministic verification engine for agents. Proves a fix: fails on the old code, passes on new. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FetchV2Fetch and extract web pages, discover links, and read llms.txt documentation indexes. | Local · stdio |
| Fetter MCPReal-time Python package and vulnerability data for AI coding agents. | Remote · HTTPLive check: ✓ handshake |
| FettleUptime monitoring for developers - monitors, incidents, heartbeats and status pages. | Remote & Local · HTTP, stdioLive check: sign-in required |