Skip to content

NanoParse

by nanoparse-dev · remote · no sign-in to list tools · v2.0.1 · published by GitHub user nanoparse-dev

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

Read only
CompareRegistry entry

2 tools: 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Only reads 2Claude Code: allow
  • nanoparse_fetchRead one URL into clean Markdown with Litmus signals (source authority, freshness, structural trust).No findings

    Why it is in this group

    • The name "nanoparse_fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    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 per month with a signed wallet (pass wallet_address + wallet_signature), or 3 anonymous free tries per network. 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.No findings

    Why it is in this group

    • The name "nanoparse_status" says "status": a word for reading.
    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.

Install

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

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

Run in a terminal.

Claude Code permissions

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

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

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as nanoparse. Review it before you use it.