API Tools

nanoparse.app

Fetches URLs and returns clean Markdown with trust indicators, while also providing quota and balance status.

1 endpoint2 known toolsFirst detected August 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://nanoparse.app/mcp

No auth detected

Capabilities

tools

Fetch a URL and return clean Markdown with Litmus (source authority, freshness, structural trust).

Inferred read-only

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

Potential side effects

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.nanoparse-mcp]
url = "https://nanoparse.app/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: nanoparse-mcp
Remote MCP URL: https://nanoparse.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "nanoparse-mcp",
  "transport": "streamable-http",
  "url": "https://nanoparse.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.