Skip to content

CleanPage MCP server

io.github.IO31-WEB/cleanpageIO31-WEBstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the CleanPage MCP server can do

The CleanPage MCP server is published by the GitHub account IO31-WEB. It has 4 tools. It can create or change data (2 tools: health and pricing), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (clean_page); 1 tool can send data out of your system (clean_page).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • healthFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free. Returns service status, version, and uptime signal. Use to check the service is reachable before paying for anything.
  • pricingFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Free. Returns current pricing, accepted payment network/asset, and the x402 payment flow details for paid tools.
Only reads 2Show 2 read-only tools
  • clean_pageFetches 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…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.
  • list_capabilitiesFree.No findings

    Why it is in this group

    • The name "list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including health (write), pricing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cleanpage https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp
claude mcp add --transport http cleanpage https://cleanpage-mcp.cleanpage-mcp.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cleanpage__list_capabilities"
    ],
    "ask": [
      "mcp__cleanpage__clean_page",
      "mcp__cleanpage__health",
      "mcp__cleanpage__pricing"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cleanpage. Review it before you use it.

Capability tags behind 1 rule
  • mcp__cleanpage__clean_page untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.IO31-WEB/cleanpage/verify?hash=97843c35df63a17ccdb64923633f1d0a74e8117d7b0e86485f0b92086b760007" | jq -e '.changed == false'

Pinned hash 97843c35df63, from Nov 15, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.IO31-WEB/cleanpage/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.IO31-WEB/cleanpage
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.IO31-WEB/cleanpage.svg)](https://radar.anlyon.com/servers/io.github.IO31-WEB/cleanpage)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.

CleanPage MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the CleanPage MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the CleanPage MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the CleanPage MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the CleanPage MCP server have?

4 tools: 2 write, 2 read. health, pricing, clean_page and list_capabilities.

Does the CleanPage MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the CleanPage MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): clean_page.

Has the CleanPage MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.