CleanPage
REMOTE · CLEANPAGE-MCP.CLEANPAGE-MCP.WORKERS.DEV
Turn any URL into clean, structured, agent-ready content. $0.02/call via x402 on Base.
Available components
Last scanned (5 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 4 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 320 tokens (~80/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cleanpage-mcp.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6074d08808a1538f0598f926908a497d922 |
| SANs: *.cleanpage-mcp.workers.dev, cleanpage-mcp.workers.dev | ||||||
| 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 cleanpage-mcp.cleanpage-mcp.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://cleanpage-mcp.cleanpage-mcp.workers.dev/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 →
clean_page ~165
Fetches a URL and returns clean, structured, agent-optimized content: readable markdown, plain text, metadata (author/date/site/word count), extracted links and images, an optional structured facts array, and a 0-100 quality score. Handles common failure modes (paywalls, bot-walls, empty JS shells) with clear typed errors instead of silently returning junk. PAID TOOL: $0.02 USDC per successful call via x402 (USDC on base). Call with no payment first to receive the exact payment requirements (HTTP 402), then retry with an X-PAYMENT header. Failed extractions are not charged.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | – | – |
| url | string | yes | Absolute URL of the page to extract (http/https only). |
No output schema declared.
No examples provided.
health ~31
Free. Returns service status, version, and uptime signal. Use to check the service is reachable before paying for anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_capabilities ~46
Free. Returns the full list of tools this server offers, including which are paid, their prices, and their input schemas — so an agent can decide what to call before spending anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pricing ~30
Free. Returns current pricing, accepted payment network/asset, and the x402 payment flow details for paid tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the CleanPage MCP server?
CleanPage is a hosted endpoint at https://cleanpage-mcp.cleanpage-mcp.workers.dev/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 · cleanpage-mcp.cleanpage-mcp.workers.dev
claude mcp add --transport http io31-web-cleanpage 'https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp'
What is the CleanPage MCP server?
CleanPage is an MCP server listed in the public MCP registry as io.github.IO31-WEB/cleanpage. Turn any URL into clean, structured, agent-ready content. $0.02/call via x402 on Base. This page covers its hosted endpoint (https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp).
Is the CleanPage MCP server safe to use?
CleanPage scores 71 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 CleanPage MCP server expose?
CleanPage exposes 4 tools: clean_page, health, list_capabilities, pricing. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.
Does the CleanPage MCP server require authentication?
No. We connected to CleanPage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CleanPage MCP server still maintained?
CleanPage is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.