nanoparse-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANOPARSE_WALLET_KEY | Yes | Base wallet private key used for x402 micropayment signing. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nanoparse_fetchA | Fetch a web page and return clean, structured Markdown with metadata. First 50 parses free per IP. After that, pay $0.0175 USDC on Base via x402. No account or API key required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or overlap. The single tool has a clearly defined purpose of fetching and converting web pages to markdown.
The tool name follows a consistent verb_noun pattern: 'nanoparse_fetch'. This is clear and predictable, though with only one tool, consistency is trivial.
Having only one tool feels thin for a server, even for a focused purpose. While the tool covers a specific function, agents might expect additional related operations or options.
For the stated purpose of fetching a web page and returning structured markdown with metadata, the single tool provides complete coverage. No other operations are necessary to fulfill the server's promise.