We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

NanoParse

MCP server by NanoParse

Read any web page into clean Markdown with source authority, freshness and paywall signals, paid per parse via x402.

No sign-in (No account or key needed)Streamable HTTP

Connect to NanoParse

No sign-in needed. Connect with NanoParse’s own URL:

https://nanoparse.app/mcp

Paste it into any client that supports remote MCP servers. Your client talks to NanoParse directly, not through mcp.tc.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/nanoparse

About

NanoParse renders a URL in a headless browser, strips navigation, ads and cookie banners, and returns clean Markdown with metadata. Each result includes Litmus signals such as source authority, freshness, paywall or truncation detection, content type, a TL;DR and key figures.

It runs as a hosted Streamable HTTP endpoint. No account, sign-in or API key is needed. The first 10 parses per network are free, then each successful parse costs $0.005 in USDC on Base via x402. Pages that cannot be read (bot wall, consent wall, paywall, PDF) are reported with a named reason and not charged.

What you can do

  • Convert one URL into clean Markdown
  • Get source authority and freshness signals
  • Detect paywalls, truncation and content type
  • Extract metadata such as author, dates and language
  • Check wallet balance and free quota before paying

Tools 2

  • nanoparse_fetchRead-only

    Read one URL into clean Markdown with Litmus signals; $0.005 per page read, first 10 free per…

  • nanoparse_statusRead-only

    Check wallet and USDC balance, quota state, and whether the next fetch will succeed without payment.

Read from the live server on 21 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

  • Read https://example.com/article into Markdown and tell me how trustworthy the source is.

  • Fetch this page and summarize the key figures, noting how fresh it is.

  • Check my NanoParse quota for my wallet address before I fetch more pages.

  • Fetch each URL in this list and flag any that are paywalled.

Set up

Every client connects to nanoparse.app. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http nanoparse https://nanoparse.app/mcp
  1. Start Claude Code and type /mcp. nanoparse should show as connected.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it NanoParse and paste this URL:
https://nanoparse.app/mcp
  1. Click Add. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://nanoparse.app/mcp and click Add.
  2. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://nanoparse.app/mcp as the server URL, then for authentication choose No authentication.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "nanoparse": {
      "url": "https://nanoparse.app/mcp"
    }
  }
}

VS Code

Or from a terminal:

code --add-mcp '{"name":"nanoparse","type":"http","url":"https://nanoparse.app/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "nanoparse": {
      "type": "http",
      "url": "https://nanoparse.app/mcp"
    }
  }
}

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "nanoparse": {
      "serverUrl": "https://nanoparse.app/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add nanoparse --url https://nanoparse.app/mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.nanoparse]
url = "https://nanoparse.app/mcp"

Gemini CLI

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

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "nanoparse": {
      "type": "http",
      "url": "https://nanoparse.app/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://nanoparse.app/mcp.

Embed

Show NanoParse in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![NanoParse on mcp.tc](https://mcp.tc/i/nanoparse/badge.svg)](https://mcp.tc/i/nanoparse)
HTML
<a href="https://mcp.tc/i/nanoparse"><img src="https://mcp.tc/i/nanoparse/badge.svg" alt="NanoParse on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/nanoparse.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/nanoparse" title="NanoParse on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/nanoparse.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the NanoParse card to your site.

Markdown
Add the mcp.tc card for NanoParse, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/nanoparse.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="nanoparse"><a href="https://mcp.tc/i/nanoparse">NanoParse on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![NanoParse on mcp.tc](https://mcp.tc/i/nanoparse/badge.svg)](https://mcp.tc/i/nanoparse)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 22 Nov 2026, 11:38 UTC.

Follow NanoParse and we’ll email you when something changes.

  1. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 14 Nov 2026, 17:57 UTC

    Changed 1

    • nanoparse_fetchdescription
      Before

      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 M…

      After

      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 M…

    Server instructions

    Before

    NanoParse reads web pages for agents. $0.005 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses a month, no account and no API key; a signed wallet claims the same 10 from a cloud host. A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature, wallet_address?, wallet_signature?) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.005. Stop any time — nothing is prepaid and nothing is held.

    After

    NanoParse reads web pages for agents. $0.002 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses a month, no account and no API key; a signed wallet claims the same 10 from a cloud host. A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature, wallet_address?, wallet_signature?) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.002. Stop any time — nothing is prepaid and nothing is held.

  2. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 25 Oct 2026, 23:37 UTC

    Changed 1

    • nanoparse_fetchdescription
      Before

      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).

      After

      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 M…

    Server instructions

    Before

    NanoParse reads web pages for agents. $0.005 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses per month with a signed wallet, or 3 anonymous free tries per network. A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature, wallet_address?, wallet_signature?) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.005. Stop any time — nothing is prepaid and nothing is held.

    After

    NanoParse reads web pages for agents. $0.005 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses a month, no account and no API key; a signed wallet claims the same 10 from a cloud host. A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature, wallet_address?, wallet_signature?) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.005. Stop any time — nothing is prepaid and nothing is held.

  3. , Automatic check

    2 tools changed.

    Details, 17 Oct 2026, 22:32 UTC

    Changed 2

    • nanoparse_fetchtitle and hints

      title

      Before

      none

      After

      Read one URL into clean Markdown + Litmus

      • readOnlyHint not set changed to yes
      • destructiveHint not set changed to no
      • openWorldHint not set changed to yes
      • idempotentHint not set changed to no
    • nanoparse_statustitle and hints

      title

      Before

      none

      After

      Check wallet, quota and payment state

      • readOnlyHint not set changed to yes
      • destructiveHint not set changed to no
      • openWorldHint not set changed to yes
      • idempotentHint not set changed to yes
  4. , Automatic check

    1 tool changed. Server instructions changed.

    New server instructions

    Details, 9 Oct 2026, 01:35 UTC

    Changed 1

    • nanoparse_fetchdescription and input schema
      Before

      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. First 10 free parses per network (subnet). 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).

      After

      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).

      • New parameters: wallet_address wallet_signature

    Server instructions

    Before

    NanoParse reads web pages for agents. $0.005 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses per network (subnet). A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.005. Stop any time — nothing is prepaid and nothing is held.

    After

    NanoParse reads web pages for agents. $0.005 per parse — paid in USDC on Base via x402, with no account, no API key and no subscription. 10 free parses per month with a signed wallet, or 3 anonymous free tries per network. A page that cannot be read — bot wall, consent wall, paywall, PDF — is reported with a named reason and never charged. Tools: nanoparse_fetch(url, payment_signature, wallet_address?, wallet_signature?) reads one page and returns clean Markdown plus Litmus signals; nanoparse_status(address) reports quota, wallet balance and payment state. Reading many pages: one call per URL, by design. Build a URL list (the site's own sitemap.xml, or your own discovery) and call nanoparse_fetch once per URL, collecting results as you go — one page per call, charged only if the read succeeds. Budget is simply pages x $0.005. Stop any time — nothing is prepaid and nothing is held.

  5. , Automatic check

    Tracking started: 2 tools.

FAQ

Can I paste mcp.tc/i/nanoparse into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://nanoparse.app/mcp, so your client talks to NanoParse directly. The quick link is for sharing: it opens this page, with setup steps for every client.

Does NanoParse need an API key or a sign-in?

No. NanoParse doesn’t ask for an account or key.

Is NanoParse a remote or a local server?

Remote. NanoParse hosts it at https://nanoparse.app/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can NanoParse do?

It has 2 tools: nanoparse_fetch and nanoparse_status. You can convert one URL into clean Markdown, get source authority and freshness signals and detect paywalls, truncation and content type.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to NanoParse?

Yes. NanoParse’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read NanoParse’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with NanoParse. This page was built from NanoParse’s public metadata, last checked on 21 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.