# CleanPage (remote · cleanpage-mcp.cleanpage-mcp.workers.dev)

Turn any URL into clean, structured, agent-ready content. $0.02/call via x402 on Base.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `cleanpage-mcp.cleanpage-mcp.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp.md), [page](https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp)

## Channel facts

- Endpoint: `https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 320 tokens (~80/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io31-web-cleanpage 'https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io31-web-cleanpage": {
      "url": "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io31-web-cleanpage": {
      "type": "http",
      "url": "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io31-web-cleanpage]
url = "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io31-web-cleanpage": {
      "type": "remote",
      "url": "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io31-web-cleanpage --url 'https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io31-web-cleanpage:
    url: "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io31-web-cleanpage": {
      "Transport": "http",
      "Url": "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io31-web-cleanpage -t streamable-http -u 'https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io31-web-cleanpage": {
      "type": "http",
      "url": "https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 57)

First indexed and scored.

## MCP tools (4)

### `clean_page` (~165 tokens)

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.

Input parameters:

- `options` (object)
- `url` (string, required): Absolute URL of the page to extract (http/https only).

### `health` (~31 tokens)

Free. Returns service status, version, and uptime signal. Use to check the service is reachable before paying for anything.

### `list_capabilities` (~46 tokens)

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.

### `pricing` (~30 tokens)

Free. Returns current pricing, accepted payment network/asset, and the x402 payment flow details for paid tools.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp#diagnostics

## Score history

- 2026-09-20: 58
- 2026-09-19: 58
- 2026-09-18: 57

## Common questions

### 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 58 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp
- Repository: https://github.com/IO31-WEB/cleanpage-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io31-web-cleanpage/cleanpage-mcp