NanoParse MCP server
online · 100% uptimeio.github.nanoparse-dev/nanoparse-mcp·v2.0.1Clean Markdown from any URL with Litmus trust signals. $0.005 per page via x402, no account.
0 stars
Reviews
Write oneNobody has reviewed NanoParse yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
NanoParse tools (2)
write = sends, deletes, buys or postsnanoparse_fetchFreeRead 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_statusFreeCheck 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.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 793ms20/20
- Tool poisoning2 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How NanoParse compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,243 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 223 ms
- faster than 63% of 30,027 servers
What its tools let an agent do: 2 read
Release history: 2 versions in the registry since 2026-08-29, latest 2026-10-06, typically one every 38 days.
Install NanoParse in Claude Code, Cursor or VS Code
claude mcp add --transport http nanoparse-mcp https://nanoparse.app/mcp
What the publisher says
From the NanoParse repository's README, as published. We do not edit it. Read it on GitHub
NanoParse MCP
The easiest way for AI agents to read the web. NanoParse MCP is a hosted Model Context Protocol server at https://nanoparse.app/mcp that turns any URL into clean Markdown your agent can actually use — with machine-readable trust signals attached.
No install. No wallet key. No .env. Connect once and your agent can read the web.
Why agents choose NanoParse over Firecrawl or Jina Reader: no account, no subscription, no API key. Pay $0.01 per parse via x402 when the free tier runs out. Full JavaScript/SPA rendering, native GFM tables, and Litmus trust signals — built for agents, not humans.
Quick start
Add this to your MCP client config:
{
"mcpServers": {
"nanoparse": {
"url": "https://nanoparse.app/mcp"
}
}
}Restart your client, and your agent auto-discovers two tools:
- nanoparsefetch(url)** — fetch any web page and get clean Markdown back
- nanoparsestatus()** — check free quota, wallet and USDC balance before spending
That's it. Your agent can now fetch pages from inside any MCP-compatible client (Claude, Cursor, Hermes, Windsurf, and others).
What you get
nanoparse_fetch renders the page in a real headless browser (JavaScript and all), isolates the actual article from nav, ads, and cookie banners, and returns:
- Clean Markdown — GFM tables, callouts, math, and footnotes preserved
- Metadata — title, author, dates, language, word count, OpenGraph, schema.org JSON-LD
- Litmus — machine-readable signals your agent can reason over: source authority, freshness, structural trust, content density, syndication and paywall detection
nanoparse_status tells your agent exactly where it stands: free parses remaining, wallet and USDC balance, and whether the next call will succeed without payment. Agents call it before spending.
Real output
Every parse returns markdown + metadata + litmus. Example — parsing an arXiv paper (examples/example-output.json, complete and unmodified):
{
"litmus": {
"source": { "type": "academic", "authority": 0.85, "rationale": "academic source" },
"freshness": { "published": null, "stale_warning": "No publish date found — verify independently" },
"tldr": "Abstract page for arXiv paper 2401.14295: Demystifying Chains, Trees, and Graphs of Thoughts",
"key_figures": [ { "value": "2,247", "context": "Thu, 25 Jan 2024 16:34:00 UTC (2,247 KB)" } ],
"content_type": "academic_paper",
"reading_time": { "minutes": 4 },
"hedge_language": { "density": "low", "markers_found": 0 },
"syndication": { "detected": false },
"paywall": { "detected": false }
}
}The agent learns before reading a word: this is an academic source (0.85 authority), no publish date was found (verify independently), here's the one-sentence summary, the key numbers, and there's no paywall or syndication flag. See examples/agent-conversation.md for a full worked round-trip.
Payments
- First 10 parses per network (subnet) are free — lifetime, shared across your whole network. No account, no API key, no human required.
- After that: $0.01 per parse (flat, no subscriptions) via x402 — an open micropayment protocol. Your agent's wallet signs the payment automatically. To give your agent a Coinbase wallet, run npx @coinbase/payments-mcp and connect it alongside NanoParse.
How payments work under the hood
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
NanoParse: common questions
- Is NanoParse MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the NanoParse safety report
- How do I install NanoParse?
- It runs remotely at nanoparse.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does NanoParse need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is NanoParse maintained?
- The last commit was 9 days ago (2026-10-27). The latest release is v2.0.1.
- Is NanoParse up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does NanoParse compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.