# NanoParse MCP server
> Read any web page into clean Markdown with source authority, freshness and paywall signals, paid per parse via x402.
- Listing: https://mcp.tc/i/nanoparse
- Connect: use the server's own URL `https://nanoparse.app/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Search & Web Data](https://mcp.tc/c/search-web)
- Vendor: NanoParse
- Homepage:
## 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 it 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_fetch`: Read one URL into clean Markdown with Litmus signals; $0.005 per page read, first 10 free per…
- `nanoparse_status`: Check wallet and USDC balance, quota state, and whether the next fetch will succeed without payment.
## 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."
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http nanoparse https://nanoparse.app/mcp
```
2. 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:
```url
https://nanoparse.app/mcp
```
3. 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:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://nanoparse.app/mcp` and click **Add**.
3. 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, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://nanoparse.app/mcp` as the server URL and choose **No authentication**.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"nanoparse": {
"url": "https://nanoparse.app/mcp"
}
}
}
```
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
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`:
```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`:
```json
{
"mcpServers": {
"nanoparse": {
"serverUrl": "https://nanoparse.app/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add nanoparse --url https://nanoparse.app/mcp
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.nanoparse]
url = "https://nanoparse.app/mcp"
```
### Gemini CLI
```bash
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.
```json
{
"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`.
## Recent changes
- 2026-10-08 04:20 UTC: Tracking started: 2 tools read. Source: automatic check.
More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/nanoparse#history (Atom feed: https://mcp.tc/i/nanoparse/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.
## Details
- Server version: 1.0.0
- MCP protocol version: 2024-11-05
- Last checked: 2026-10-08 (reachable)
- Listed: 2026-10-08
- Updated: 2026-10-08
---
Source: https://mcp.tc/i/nanoparse (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report