NanoParse
NanoParse is an MCP server on Base.
- Sato Score79
- ChainsBase
NanoParse is an open-source MCP server on Base, with last code activity on 2026-10-11 (Active). Sato Score 79/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-14. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Oct 11, 2026
Listed from nanoparse.app on 2026-10-14. Install: not attempted — no install path on record. Evidence →
Next step
Watch NanoParse
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on nanoparse-dev/nanoparse-mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
https://nanoparse.app answered on 2026-10-14 (page title: "NanoParse — Parse the Web"). Source is public at nanoparse-dev/nanoparse-mcp (MIT, 0★); created 2026-08-02, last pushed 2026-10-11. Documentation at https://nanoparse.app/quickstart answered on 2026-10-14. An MCP initialize handshake against https://nanoparse.app/mcp completed on 2026-10-14 and listed 2 tools. One unpaid request to https://nanoparse.app/fetch answered HTTP 402 with a payment payload we could parse (network eip155:8453, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). No payment was sent: a 402 says the endpoint asked for money in a readable shape, not that paying works or that the seller delivers. The host serves an x402 capability manifest at /.well-known/x402. Listed from a maintainer submission; every field is self-reported except the checks above, which Sato Hub ran itself on 2026-10-14.
Sato Score
79/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 16/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 6/15
- Independent verification
- 6/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from nanoparse.app on 2026-10-14. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Base | self-reported | nanoparse.app | as of 2026-10-14 |
| Verification status | Self-Reported — not independently reviewed | self-reported | nanoparse.app | as of 2026-10-14 |
| Recent activity | last commit 2026-10-11 | observed | github.com/nanoparse-dev/nanoparse-mcp | 2026-10-14 |
| MCP endpoint answers | answered — 2 tools listed | observed | nanoparse.app | 2026-10-14 |
| ERC-8004 registration | declared address not found in the registry | observed | — | 2026-10-14 |
| Description | text setconfidence 1.00 | self-reported | — | as of 2026-10-14 |
| Sato Score | 79/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-14 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Tool inventory — 2 tools, probed live 2026-10-14
nanoparse_fetch— 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 wnanoparse_status— 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.
- Answers a handshake
- yes · 2026-10-14
- Answers a call
- not asked — no tool is named as a read (list_/get_/search_)
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
Observed record — 1 daily check since 2026-10-14
- Succeeded
- 1
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.
Details
- Chains
- Base
- Open source
- Yes
- Last checked
- 2026-10-14
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Listing History
Recorded changes to NanoParse's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 14, 2026Listed on Sato Hub
- Oct 14, 2026Sato Hub began tracking this listing
- Oct 14, 2026Updated: description long
Compared with
Appears in
- x402 payment tools on Base, scored →
- Base MCP servers, scored →
- x402-ready tools, scored →
- Payment tools for agents, scored →
- Hosted MCP endpoints answering today, scored →
- Base MCP servers you can use without a local server →
- x402 endpoints checked for a payment-required answer →
- x402 facilitators on Base →
- x402: agent payments over HTTP →
- MCP: the tool interface for agents →
- Onchain agents on Base →
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about NanoParse
- Is NanoParse open source?
- Yes. NanoParse is open source; the repository is https://github.com/nanoparse-dev/nanoparse-mcp. Checked as of 2026-10-14.
- Which chains does NanoParse support?
- NanoParse lists support for Base as of 2026-10-14.
- Is NanoParse still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-11 (last commit 2026-10-11), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run NanoParse?
- Sato Hub has no deploy spec for NanoParse; follow the project's own documentation at https://nanoparse.app/quickstart.
- Is NanoParse verified on Sato Hub?
- Sato Hub holds one earned check for NanoParse: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 79 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "NanoParse — Sato Hub." Sato Hub, updated 2026-10-14, accessed 2026-10-14. https://satohub.ai/resources/nanoparseData last refreshed 2026-10-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.