ai.clawfetch/mcp
REMOTE · MCP.CLAWFETCH.AI · 2 COMPONENTS · SCANNED SEP 21
Web intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys.
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 Security57
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the ai.clawfetch/mcp server?
ai.clawfetch/mcp is a hosted endpoint at https://mcp.clawfetch.ai/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 · mcp.clawfetch.ai
claude mcp add --transport http ai-clawfetch-mcp 'https://mcp.clawfetch.ai/mcp'
{
"mcpServers": {
"ai-clawfetch-mcp": {
"url": "https://mcp.clawfetch.ai/mcp"
}
}
} {
"servers": {
"ai-clawfetch-mcp": {
"type": "http",
"url": "https://mcp.clawfetch.ai/mcp"
}
}
} [mcp_servers.ai-clawfetch-mcp] url = "https://mcp.clawfetch.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-clawfetch-mcp": {
"type": "remote",
"url": "https://mcp.clawfetch.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-clawfetch-mcp --url 'https://mcp.clawfetch.ai/mcp' --transport streamable-http
mcp_servers:
ai-clawfetch-mcp:
url: "https://mcp.clawfetch.ai/mcp" {
"McpServers": {
"ai-clawfetch-mcp": {
"Transport": "http",
"Url": "https://mcp.clawfetch.ai/mcp"
}
}
} assistant mcp add ai-clawfetch-mcp -t streamable-http -u 'https://mcp.clawfetch.ai/mcp'
{
"mcpServers": {
"ai-clawfetch-mcp": {
"type": "http",
"url": "https://mcp.clawfetch.ai/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.
- 18 Sept 26 −58
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 4 Sept 26 +1
- Stability: 0.97 → pass security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 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.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 0
- Tool “check_domains” rewrote its description, which is the text the model reads security
- Tool “extract_data” rewrote its description, which is the text the model reads security
- Tool “parse_document” 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 “research_topic” rewrote its description, which is the text the model reads security
- Tool “suggest_domains” rewrote its description, which is the text the model reads security
- Server version: 0.2.0 → 0.3.1 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 21 Sept 2026 · Probed https://mcp.clawfetch.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.clawfetch.ai | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 667d76d9924a076b5aa518873b7dce83756 |
| SANs: mcp.clawfetch.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.clawfetch.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| clawfetch.ai. | 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 | 410 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.clawfetch.ai/mcp | HTTP error | 410 | |
| http (plaintext) | http://mcp.clawfetch.ai/mcp | HTTPS enforced | 301 | https://mcp.clawfetch.ai/mcp |
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_domains ~54
Check if one or more domain names are available for registration. Cost: $0.008 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Array of domain names to check (e.g., ["example.com", "myapp.io"]) |
No output schema declared.
No examples provided.
extract_data ~134
Extract structured data from a URL using a specialized extractor. Supports 17+ site types including GitHub repos/profiles, npm packages, Twitter/X profiles, LinkedIn, YouTube, Product Hunt, Hacker News, Reddit, and more. Cost: $0.008 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | – | Optional extractor override (e.g. "github", "coingecko"). Auto-detected from the URL when omitted. |
| url | string | yes | The URL to extract data from (e.g., "https://github.com/openai/openai-python", "https://www.npmjs.com/package/express") |
No output schema declared.
No examples provided.
fetch_url ~77
Fetch a URL and return its content as clean markdown. Works for articles, docs, blogs, product pages — any static HTML. Cost: $0.001 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | number | – | Maximum characters to return (default: no limit). Use to control response size. |
| url | string | yes | The URL to fetch |
No output schema declared.
No examples provided.
health_check ~25
Check the ClawFetch API health status. Free — no x402 payment required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_extractors ~45
List all available structured data extractors with their supported domains and fields. Use this to discover what sites ClawFetch can extract typed data from. Cost: $0.001.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parse_document ~168
Parse an office document (docx, pptx, xlsx, pdf, odt, ods, odp, rtf, epub, csv, doc, ppt) into clean GitHub-Flavored Markdown. Provide a document URL or a local file path. Deterministic Rust converter — headings, tables, and lists preserved. No OCR: scanned/image-only PDFs are rejected. Cost: $0.005 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Optional explicit format override (e.g. "csv"). Auto-detected from bytes/extension when omitted. |
| path | string | – | Local file path of the document to parse (read and uploaded as bytes) |
| url | string | – | URL of the document to download and parse (e.g. "https://example.com/report.docx") |
No output schema declared.
No examples provided.
render_page ~98
Render a JavaScript-heavy page using a stealth browser and return clean markdown. Use for SPAs, React/Vue/Angular apps, pages behind JS rendering. Cost: $0.005 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | number | – | Maximum characters to return |
| url | string | yes | The URL to render |
| waitFor | string | – | CSS selector to wait for before extracting content (e.g., ".main-content", "#app") |
No output schema declared.
No examples provided.
research_topic ~93
Research a topic using multiple sources. Returns a summary with cited sources. Great for market research, competitive analysis, fact-checking, and current events. Cost: $0.02 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | number | – | Number of sources to consult (default: 5, max: 10) |
| topic | string | yes | The topic or question to research (e.g., "latest developments in AI agent frameworks") |
No output schema declared.
No examples provided.
suggest_domains ~103
Generate available domain name suggestions based on a keyword or concept. Cost: $0.008 per request.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of suggestions to generate (default: 10) |
| query | string | yes | Keyword or concept to generate domain suggestions for (e.g., "ai agent marketplace") |
| tlds | array | – | Preferred TLDs to check (e.g., [".com", ".io", ".ai"]). Default: common TLDs. |
No output schema declared.
No examples provided.
wallet_info ~28
Get the wallet address being used for x402 payments. Useful for checking balance or funding the wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ai.clawfetch/mcp server?
ai.clawfetch/mcp is listed in the public MCP registry as ai.clawfetch/mcp. Web intelligence for AI agents: fetch, render, extract, research. x402 micropayments, no API keys. This page covers its hosted endpoint (https://mcp.clawfetch.ai/mcp).
Is the ai.clawfetch/mcp server safe to use?
ai.clawfetch/mcp scores 23 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 ai.clawfetch/mcp server expose?
ai.clawfetch/mcp exposes 10 tools: fetch_url, render_page, research_topic, check_domains, suggest_domains, and 5 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Does the ai.clawfetch/mcp server require authentication?
No. We connected to ai.clawfetch/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.clawfetch/mcp server still maintained?
ai.clawfetch/mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.