NanoParse MCP
REMOTE · NANOPARSE.APP · SCANNED SEP 20
Fetch any web page to clean Markdown with Litmus trust signals. No account or API key needed.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 221 tokens (~110/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the NanoParse MCP server?
NanoParse MCP 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'
{
"mcpServers": {
"nanoparse-dev-nanoparse-mcp": {
"url": "https://nanoparse.app/mcp"
}
}
} {
"servers": {
"nanoparse-dev-nanoparse-mcp": {
"type": "http",
"url": "https://nanoparse.app/mcp"
}
}
} [mcp_servers.nanoparse-dev-nanoparse-mcp] url = "https://nanoparse.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nanoparse-dev-nanoparse-mcp": {
"type": "remote",
"url": "https://nanoparse.app/mcp",
"enabled": true
}
}
} openclaw mcp add nanoparse-dev-nanoparse-mcp --url 'https://nanoparse.app/mcp' --transport streamable-http
mcp_servers:
nanoparse-dev-nanoparse-mcp:
url: "https://nanoparse.app/mcp" {
"McpServers": {
"nanoparse-dev-nanoparse-mcp": {
"Transport": "http",
"Url": "https://nanoparse.app/mcp"
}
}
} assistant mcp add nanoparse-dev-nanoparse-mcp -t streamable-http -u 'https://nanoparse.app/mcp'
{
"mcpServers": {
"nanoparse-dev-nanoparse-mcp": {
"type": "http",
"url": "https://nanoparse.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 · 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 | 19 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | aa95134fe46a35c313d64b6ad086a041 |
| 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 insecure
Validation of nanoparse.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nanoparse.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 | Served over HTTP | 200 |
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 ~159
Fetch a URL and return clean Markdown with Litmus (source authority, freshness, structural trust). First 10 free parses per network (subnet), then $0.01 per request via x402 micropayment — 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| content | array | yes | 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 |
|---|---|---|---|
| content | array | yes | Human-readable status report as text content |
| structuredContent | object | – | Machine-readable status fields |
No examples provided.
What is the NanoParse MCP server?
NanoParse MCP is listed in the public MCP registry as io.github.nanoparse-dev/nanoparse-mcp. Fetch any web page to clean Markdown with Litmus trust signals. No account or API key needed. This page covers its hosted endpoint (https://nanoparse.app/mcp).
Is the NanoParse MCP server safe to use?
NanoParse MCP scores 67 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 MCP exposes 2 tools: nanoparse_fetch, nanoparse_status. Their descriptions and schemas cost roughly 221 tokens of context every time the server is loaded.
Does the NanoParse MCP server require authentication?
No. We connected to NanoParse MCP 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 MCP 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.