Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.damonwill78-a11y/clean-markdown

NPM · CLEAN-MARKDOWN-MCP · SCANNED SEP 20

Any URL to clean, LLM-ready Markdown for RAG. Strips ads, nav, and boilerplate.

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security93
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects stream-json 1.9.1, reached via apify > @crawlee/core > stream-json. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 90 of 299 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 138 tokens (~138/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.damonwill78-a11y/clean-markdown MCP server?

io.github.damonwill78-a11y/clean-markdown runs locally as an npm package, launched with npx -y clean-markdown-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · clean-markdown-mcp

# add to Claude Code
claude mcp add damonwill78-a11y-clean-markdown -- npx -y clean-markdown-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "damonwill78-a11y-clean-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "clean-markdown-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "damonwill78-a11y-clean-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "clean-markdown-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add damonwill78-a11y-clean-markdown -- npx -y clean-markdown-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "damonwill78-a11y-clean-markdown": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "clean-markdown-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add damonwill78-a11y-clean-markdown --command npx --arg -y --arg clean-markdown-mcp
# ~/.hermes/config.yaml
mcp_servers:
  damonwill78-a11y-clean-markdown:
    command: "npx"
    args: ["-y", "clean-markdown-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "damonwill78-a11y-clean-markdown": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "clean-markdown-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add damonwill78-a11y-clean-markdown -t stdio -c npx -a -y clean-markdown-mcp
// mcp.json
{
  "mcpServers": {
    "damonwill78-a11y-clean-markdown": {
      "command": "npx",
      "args": [
        "-y",
        "clean-markdown-mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 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.

  • 19 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 16 Sept 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 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 13 Sept 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.

Diagnostics

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 20 Sept 2026 · Analysed npm/clean-markdown-mcp@1.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-3p6v-hrg8-8qj7 CVE-2025-2792 low yes
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 299 packages
Packages resolved 299
Deprecated 2
Stale 90
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~138 tokens

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 →

Tool Tokens
scrape_url ~138

Fetch any web page and return its main content as clean, readable Markdown. Strips out navigation, ads, cookie banners, scripts, and other boilerplate. Ideal for feeding article or documentation content to an LLM.

NameTypeReqDescription
includeLinksbooleanKeep hyperlinks in the output (default true). Set to false for cleaner plain prose.
renderJsbooleanRender the page in a real browser first (default false). Use for sites whose content is built by JavaScript. Requires Playwright to be installed.
urlstringyesThe full URL of the web page to scrape (must start with http:// or https://).

No output schema declared.

No examples provided.

Common questions

What is the io.github.damonwill78-a11y/clean-markdown MCP server?

io.github.damonwill78-a11y/clean-markdown is an MCP server listed in the public MCP registry as io.github.damonwill78-a11y/clean-markdown. Any URL to clean, LLM-ready Markdown for RAG. Strips ads, nav, and boilerplate. This page covers its npm package (clean-markdown-mcp).

Is the io.github.damonwill78-a11y/clean-markdown MCP server safe to use?

io.github.damonwill78-a11y/clean-markdown scores 83 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.damonwill78-a11y/clean-markdown MCP server expose?

io.github.damonwill78-a11y/clean-markdown exposes 1 tool: scrape_url. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.

Is the io.github.damonwill78-a11y/clean-markdown MCP server still maintained?

io.github.damonwill78-a11y/clean-markdown 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.

What licence is the io.github.damonwill78-a11y/clean-markdown MCP server under?

io.github.damonwill78-a11y/clean-markdown declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.