@readfetch/mcp-x402-proxy
Related Servers
Alternatives to @readfetch/mcp-x402-proxy
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.3215,256 npm5,681MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents scrape web pages as clean markdown for a micro-payment in USDC, using the x402 protocol on Base network. No API keys or signup required.MIT
Related Servers

halowerk-mcpofficial
AlicenseAqualityDmaintenanceProvides access to 70 paid APIs as MCP tools with per-call and session budgets, paying via x402/USDC on Base without requiring an account or login. Includes a built-in allowlist of hosts and safe defaults to prevent unintended payments.1482 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to call pay-per-use tools for search, PDF processing, web reading, extraction, summarization, fact-checking, translation, jobs, and discovery, with each call paid in USDC on Base via x402 and no API key or account required.AGPL 3.0
- AlicenseAqualityFmaintenanceEnables MCP clients to access all endpoints of an x402 gateway by paying real-time microtransactions (USDC on Base) per API call, with automatic tool discovery and spend guardrails.23MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI hosts to access URL extraction, Python security scanning, email validation, domain intelligence, and PDF inspection/extraction tools, with automatic per-call USDC payments on Base.27 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables existing MCP clients to access paid MCP servers by signing x402 payments locally and proxying tool calls, with automatic line management, retries, and spend limits.25 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceA local MCP proxy that connects to remote MCP servers and automatically handles x402 payments, signing USDC on-chain when a tool returns HTTP 402.1MIT
TDQS
Scored across 15 tools
Many tools perform related extraction work (text, scrape, residential, fetch, batch), but each description explicitly states when to prefer it and points to alternatives. The main residual ambiguity is scrape vs residential, which have nearly identical request/response shapes differentiated only by egress.
All tools use a consistent readfetch_ snake_case prefix with descriptive suffixes, and no mixed casing or verb-style conventions appear. The suffixes mix nouns and actions, but the overall pattern is predictable and readable.
15 tools is at the upper end but appropriate for a broad web-acquisition suite covering text, scraping, PDFs, screenshots, search, crawling, and raw HTTP. Each route has a distinct role, though the surface is dense.
Coverage is broad: single-URL extraction, JS rendering, raw HTTP, PDFs, screenshots, batch reads, search, site mapping, async crawl with status polling, diffing, section extraction, probing, and feedback. Minor gaps include no crawl cancellation or structured/table extraction mode, but core workflows are covered.