cloud.fetcher/fetcher
REMOTE · API.FETCHER.CLOUD · SCANNED SEP 20
The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1336 tokens (~70/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the cloud.fetcher/fetcher MCP server?
cloud.fetcher/fetcher is a hosted endpoint at https://api.fetcher.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.fetcher.cloud
claude mcp add --transport http cloud-fetcher-fetcher 'https://api.fetcher.cloud/mcp'
{
"mcpServers": {
"cloud-fetcher-fetcher": {
"url": "https://api.fetcher.cloud/mcp"
}
}
} {
"servers": {
"cloud-fetcher-fetcher": {
"type": "http",
"url": "https://api.fetcher.cloud/mcp"
}
}
} [mcp_servers.cloud-fetcher-fetcher] url = "https://api.fetcher.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud-fetcher-fetcher": {
"type": "remote",
"url": "https://api.fetcher.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add cloud-fetcher-fetcher --url 'https://api.fetcher.cloud/mcp' --transport streamable-http
mcp_servers:
cloud-fetcher-fetcher:
url: "https://api.fetcher.cloud/mcp" {
"McpServers": {
"cloud-fetcher-fetcher": {
"Transport": "http",
"Url": "https://api.fetcher.cloud/mcp"
}
}
} assistant mcp add cloud-fetcher-fetcher -t streamable-http -u 'https://api.fetcher.cloud/mcp'
{
"mcpServers": {
"cloud-fetcher-fetcher": {
"type": "http",
"url": "https://api.fetcher.cloud/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Aug 26 +1
- Stability: 0.97 → pass security
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1130 → 1336 ▼ functional
- New tool “guard_inspect” functional
- New tool “guard_tx” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Tool “check_domain” rewrote its description, which is the text the model reads security
- Tool “check_robots” rewrote its description, which is the text the model reads security
- Tool “diff_pages” rewrote its description, which is the text the model reads security
- Tool “dns_lookup” rewrote its description, which is the text the model reads security
- Tool “extract_content” rewrote its description, which is the text the model reads security
- Tool “extract_pdf” rewrote its description, which is the text the model reads security
- Tool “find_favicon” rewrote its description, which is the text the model reads security
- Tool “generate_qr” rewrote its description, which is the text the model reads security
- Tool “get_feed” rewrote its description, which is the text the model reads security
- Tool “get_oembed” rewrote its description, which is the text the model reads security
- Tool “inspect_headers” rewrote its description, which is the text the model reads security
- Tool “render_page” rewrote its description, which is the text the model reads security
- Tool “resolve_url” rewrote its description, which is the text the model reads security
- Tool “screenshot_page” rewrote its description, which is the text the model reads security
- Tool “ssl_lookup” rewrote its description, which is the text the model reads security
- Tool “unfurl_url” rewrote its description, which is the text the model reads security
- Tool “whois_lookup” rewrote its description, which is the text the model reads security
- Schema quality: 44 → 66 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → fair functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.fetcher.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fetcher.cloud | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | b9eb27ec54cd6f4a0e24593efd8fc8a8 |
| SANs: fetcher.cloud, api.fetcher.cloud, *.api.fetcher.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.fetcher.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| fetcher.cloud. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.fetcher.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://api.fetcher.cloud/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain ~77
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).
| Name | Type | Req | Description |
|---|---|---|---|
| enriched | boolean | – | – |
| name | string | yes | – |
| tlds | array | – | – |
No output schema declared.
No examples provided.
check_robots ~77
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).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Target URL or hostname. |
| path | string | – | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
diff_pages ~67
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).
| Name | Type | Req | Description |
|---|---|---|---|
| url_a | string | yes | Target URL or hostname. |
| url_b | string | – | – |
No output schema declared.
No examples provided.
dns_lookup ~67
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).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
extract_content ~61
Extract a page's main content as clean Markdown + text with metadata. (content; $0.005/call in USDC via x402, 30 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
extract_pdf ~61
Extract text + metadata from a PDF URL (text-based PDFs). (content; $0.01/call in USDC via x402, 20 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | number | – | – |
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
find_favicon ~50
Find a site's best icon/logo. (web-intel; $0.002/call in USDC via x402, 50 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
generate_qr ~57
Generate a QR code (SVG) for text or a URL. (utility; $0.002/call in USDC via x402, 50 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | – |
| ecc | string | – | – |
No output schema declared.
No examples provided.
get_feed ~60
Discover and parse a site's RSS/Atom feed into JSON items. (content; $0.003/call in USDC via x402, 40 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
get_oembed ~62
Rich embed (oEmbed) data for a media URL (YouTube, Vimeo, X, Spotify...). (content; $0.002/call in USDC via x402, 50 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
guard_inspect ~98
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 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Use the ML classifier too (default true). |
| text | string | yes | Untrusted content to screen. |
No output schema declared.
No examples provided.
guard_tx ~109
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).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | string | – | Calldata (0x...). |
| from | string | – | – |
| to | string | yes | – |
| value | string | – | Native value in wei. |
No output schema declared.
No examples provided.
inspect_headers ~53
HTTP response headers + security-header analysis for a URL. (web-intel; $0.002/call in USDC via x402, 50 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
render_page ~74
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).
| Name | Type | Req | Description |
|---|---|---|---|
| full_page | boolean | – | – |
| screenshot | boolean | – | – |
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
resolve_url ~59
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).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
screenshot_page ~63
Screenshot a page (real browser) as a base64 PNG/JPEG. (browser; $0.02/call in USDC via x402, 10 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| full_page | boolean | – | – |
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
ssl_lookup ~58
TLS certificate details (issuer, expiry, SANs) via Certificate Transparency logs. (domain-dns; $0.004/call in USDC via x402, 40 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
unfurl_url ~57
Link preview card (title, description, image, favicon) for any URL. (content; $0.003/call in USDC via x402, 50 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target URL or hostname. |
No output schema declared.
No examples provided.
whois_lookup ~58
Deep domain registration record via RDAP (registrar, dates, nameservers, DNSSEC). (domain-dns; $0.005/call in USDC via x402, 40 free/day).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
What is the cloud.fetcher/fetcher MCP server?
cloud.fetcher/fetcher is an MCP server listed in the public MCP registry as cloud.fetcher/fetcher. The web capability layer for AI agents: render, extract, DNS, SSL, WHOIS & more via x402. This page covers its hosted endpoint (https://api.fetcher.cloud/mcp).
Is the cloud.fetcher/fetcher MCP server safe to use?
cloud.fetcher/fetcher scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the cloud.fetcher/fetcher MCP server expose?
cloud.fetcher/fetcher exposes 19 tools: render_page, screenshot_page, extract_content, resolve_url, unfurl_url, and 14 more. Their descriptions and schemas cost roughly 1,268 tokens of context every time the server is loaded.
Does the cloud.fetcher/fetcher MCP server require authentication?
No. We connected to cloud.fetcher/fetcher without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cloud.fetcher/fetcher MCP server still maintained?
cloud.fetcher/fetcher is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.