mcpbeat Sign in

NanoParse MCP Server

by nanoparse-dev Your server? Claim it
answering

NanoParse is answering right now. Last checked 8 min ago. It exposes 2 tools. Last commit 27 Oct 2026.

Clean Markdown from any URL with Litmus trust signals. $0.005 per page via x402, no account.

Uptime history 71 days of history · worst day 92%
71 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
225 ms
Response time
average over 24h
0
Stars
last commit 27 Oct 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 October 2026. No other catalogue keeps this.

25 Oct a tool description was rewritten nanoparse_fetch
9 Oct a tool description was rewritten nanoparse_fetch
9 Oct a tool changed the parameters it asks for nanoparse_fetch
6 Oct a tool description was rewritten2 times that day nanoparse_fetch
and 1 more, back to 6 October 2026

Nothing serious here today

Today is the operative word: we check NanoParse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add nanoparse-mcp --transport http https://nanoparse.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://nanoparse.app/mcp
~/.codex/config.toml
[mcp_servers.nanoparse-mcp]
url = "https://nanoparse.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nanoparse-mcp": {
      "url": "https://nanoparse.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nanoparse-mcp": {
      "type": "http",
      "url": "https://nanoparse.app/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nanoparse
nanoparse_fetch
Read one URL into clean Markdown with Litmus signals (source authority, freshness, structural trust). Price: $0.005 per page actually read, USDC on Base via x402. Free tier: 10 free parses a month, no account and no key. On a cloud host (where the anonymous allowance does not apply) pass wallet_address + wallet_signature once — a plain EIP-191 signature, no payment — to claim the same 10. A page we cannot read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. To read a whole site or a list: call this tool once per URL. Build your list first (GET https://<site>/sitemap.xml, or use URLs you already have), then loop. No minimum, no commitment, no balance to spend down: stop whenever you like. If you already know the price and the payTo address, pay on the first call and skip the 402 round trip. Otherwise, when the tool returns a payment_required error, sign the included payment_terms and retry with the payment_signature argument (works in every MCP client; no custom headers needed).
nanoparse_status
Check wallet balance, USDC balance, quota state, and whether the next /fetch call will succeed without payment. Use before spending — tells the agent exactly how much to fund.

Endpoints

URLTransportStateLatencyChecked
https://nanoparse.app/mcp streamable-http answering 240 ms 8 min ago

Alternatives to NanoParse

same job, measured the same way
402scrape
by redsoukas

Clean Markdown from any webpage and live crypto prices. Paid per call via x402 (USDC on Base).

593 installs/wk local only
X
x402 Markdown Reader
by workers-xbtbot-x402-reader

Turn any public web page into clean Markdown. Pay-per-call via x402: 0.005 USDC on Base.

2 tools answering
Avo Cado Read
by workers-a-347-avocado-read-api

Web page to clean Markdown for agents. Pay per call ($0.003 USDC on Base) via x402.

2 tools answering
Geo402 Geo Web Fetch
by geo402

Read any public web page as seen from another country, as clean markdown. Pay per page.

465 installs/wk local only
Web Page Fetcher
by paimonchan

Fetch web pages with SSRF protection. Returns clean, readable markdown from any URL.

local only
M
mdapi — HTML to Markdown for AI agents
by fastdb-md

Web page or HTML to clean LLM-ready Markdown or JSON. x402 pay-per-call, $0.005, no API key.

3 tools answering
Pagemd
by kaneky

Read any public web page as clean Markdown for LLMs, with its metadata. Paid per call, x402.

1 tools answering
X
X1-BaaS Scraping API
by tazpal

Stealth scraping API for AI agents. Clean Markdown from any URL. x402 crypto payments.

3 tools answering

NanoParse — questions

Answers built from our own checks of this server.

What can NanoParse do?
It exposes 2 tools, read directly from the server on our last check. Among them: nanoparse_fetch, nanoparse_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is NanoParse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 225 ms. The bar chart above shows every period we have measured.
How do I connect NanoParse?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does NanoParse need an API key?
No. NanoParse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is NanoParse?
It answers our handshake in 225 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is NanoParse open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at nanoparse.app, which runs on its operator's own terms.