Skip to content

NanoParse MCP server

io.github.nanoparse-dev/nanoparse-mcpnanoparse-devstreamable-httpv2.0.2Scanned

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

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the NanoParse MCP server can do

The NanoParse MCP server is published by the GitHub account nanoparse-dev. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (nanoparse_fetch and nanoparse_status); 1 tool can send data out of your system (nanoparse_fetch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 2.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • nanoparse_fetchRead one URL into clean Markdown with Litmus signals (source authority, freshness, structural trust).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "nanoparse_fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Read one URL into clean Markdown with Litmus signals (source authority, freshness, structural trust). Price: $0.002 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).

    Annotations the server declares

    • title: Read one URL into clean Markdown + Litmus
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • nanoparse_statusCheck wallet balance, USDC balance, quota state, and whether the next /fetch call will succeed without payment.Reads text others writeNo findings

    Why it is in this group

    • The name "nanoparse_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check wallet, quota and payment state
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 2.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http nanoparse https://nanoparse.app/mcp
claude mcp add --transport http nanoparse https://nanoparse.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nanoparse__nanoparse_status"
    ],
    "ask": [
      "mcp__nanoparse__nanoparse_fetch"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nanoparse. Review it before you use it.

Capability tags behind 2 rules
  • mcp__nanoparse__nanoparse_fetch untrusted-input, outbound
  • mcp__nanoparse__nanoparse_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.nanoparse-dev/nanoparse-mcp/verify?hash=7a89252b8840b40c845a02736f1f1faf4db230e8560dc717dc6523fcebe4e08e" | jq -e '.changed == false'

Pinned hash 7a89252b8840, from Nov 14, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.nanoparse-dev/nanoparse-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.nanoparse-dev/nanoparse-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.nanoparse-dev/nanoparse-mcp.svg)](https://radar.anlyon.com/servers/io.github.nanoparse-dev/nanoparse-mcp)

Source: MCP Registry · repository. Synced Nov 14, 2026, 19:18 UTC.

NanoParse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NanoParse MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the NanoParse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NanoParse MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the NanoParse MCP server have?

2 tools: 2 read. nanoparse_fetch and nanoparse_status.

Does the NanoParse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the NanoParse MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): nanoparse_fetch.

Has the NanoParse MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.