ai.clawfetch/mcp
REMOTE · MCP.CLAWFETCH.AI · 2 COMPONENTS · SCANNED AUG 7
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 →
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 call this server, and 10 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 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 899 tokens (~64/item across 14 items; 10 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.clawfetch.ai
claude mcp add --transport http ai-clawfetch-mcp 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": {
"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.
- 7 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Aug 26 +6
- Schema quality: 56 → 64 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- New tool “parse_document” functional
- 5 Aug 26 59
First indexed and scored.
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 7 Aug 2026 · Probed https://mcp.clawfetch.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| 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 |
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 | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.clawfetch.ai/mcp | Verified | 200 | |
| 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.
check_domains ~54
Check if one or more domain names are available for registration. Cost: $0.002 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.003 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.002 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.002 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.01 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.002 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.