NanoParse
REMOTE · NANOPARSE.APP
Clean Markdown from any URL with Litmus trust signals. $0.005 per page via x402, no account.
Available components
Last scanned (17 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Web Scraping
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 691 tokens (~345/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “nanoparse_fetch” rewrote its description, which is the text the model reads security
- 18 Oct 26 +10
- Authorization: unverified → partial ▲ security
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2024-11-05 → 2025-11-25 functional
- 13 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- 10 Oct 26 +2
- HTTPS: fail → pass ▲ security
- Schema quality: pass → fail ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Probed https://nanoparse.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nanoparse.app | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 99d9530d6a2365a513f9fc877666f7b0 |
| SANs: nanoparse.app, www.nanoparse.app, *.www.nanoparse.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of nanoparse.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nanoparse.app. | present | 2371 | 13 | Verified |
| nanoparse.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nanoparse.app/mcp | Verified | 200 | |
| http (plaintext) | http://nanoparse.app/mcp | HTTPS enforced | 308 | https://nanoparse.app/mcp |
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 →
nanoparse_fetch ~416
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).
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | – | x402 payment signature — base64-encoded JSON payment terms. Only needed after the free tier is exhausted: the payment_required error response includes the payment_terms to sign. Pass the signed terms… |
| url | string | yes | The URL to fetch and parse |
| wallet_address | string | – | Your wallet address (0x...) to claim the free tier — no payment needed. |
| wallet_signature | string | – | EIP-191 personal_sign signature (0x... hex, 65 bytes r||s||v) over the exact string "nanoparse.app free tier: sign this message to claim 10 free parses (no payment).". Proves you own wallet_address a… |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | – | Array of content items returned by the tool |
No examples provided.
nanoparse_status ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | The Ethereum wallet address to query (0x...). |
| Name | Type | Req | Description |
|---|---|---|---|
| balance_error | string|null | – | – |
| balance_known | boolean | – | – |
| estimated_parses_remaining | number|null | – | null when the balance is unknown — never 0, which would imply an empty wallet |
| funding_uri | string | – | – |
| next_call_will_succeed | boolean|null | – | null when the free tier is exhausted and the balance is unknown |
| price_per_parse | string | yes | – |
| quota | object | yes | – |
| usdc_balance | string | yes | – |
| usdc_balance_raw | string|null | – | Balance in micro-USDC; null when the chain could not be read |
| wallet_address | string | yes | – |
No examples provided.
How do I install the NanoParse MCP server?
NanoParse is a hosted endpoint at https://nanoparse.app/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.
remote · nanoparse.app
claude mcp add --transport http nanoparse-dev-nanoparse-mcp 'https://nanoparse.app/mcp'
What is the NanoParse MCP server?
NanoParse is an MCP server listed in the public MCP registry as io.github.nanoparse-dev/nanoparse-mcp. Clean Markdown from any URL with Litmus trust signals. $0.005 per page via x402, no account. This page covers its hosted endpoint (https://nanoparse.app/mcp).
Is the NanoParse MCP server safe to use?
NanoParse scores 84 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 NanoParse MCP server expose?
NanoParse exposes 2 tools: nanoparse_fetch, nanoparse_status. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.
Does the NanoParse MCP server require authentication?
No. We connected to NanoParse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NanoParse MCP server still maintained?
NanoParse is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.