Backfill Fetch
Server Details
Pay-per-fetch web extraction for agents: POST a URL, get clean markdown. x402 USDC on Base.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools are mostly distinct: fetch_page returns readable markdown, while extract_data returns schema-shaped JSON. Both perform web fetching and share escalation behavior, so an agent could initially hesitate, but the output formats and descriptions clarify the boundary.
Both names follow a clear verb_noun snake_case pattern: extract_data and fetch_page. There is no mixing of conventions or vague naming.
Two tools is quite thin for a fetch/extraction service, even a narrow one. The set is coherent and each tool earns its place, but the surface feels minimal and relies on the paid HTTP API for any non-free operation.
The core use cases of fetching readable page content and extracting structured data are covered. Minor gaps exist around batch fetching, crawling, or richer fetch metadata, and paid operations are intentionally delegated to the HTTP API rather than exposed over MCP.
Available Tools
2 toolsextract_dataAInspect
Extract structured data from a web page, returned as JSON matching a JSON Schema you supply, via Backfill Extract. The service fetches the URL (a plain fetch first, with escalation when the plain fetch returns a bot wall or a JavaScript shell) and extracts the data described by the schema. Extraction is always a paid call (x402, USDC on Base: $0.15 fresh, $0.05 for a cached result), so a call over MCP returns an error directing you to the paid HTTP API at POST https://backfill.top/v1/extract; payment is never attempted over MCP.
Inputs: url (required), schema (required), mode.
fetch_pageAInspect
Fetch a web page and return its readable content as clean markdown, via Backfill Fetch. The service fetches the URL (a plain fetch first, with escalation when the plain fetch returns a bot wall or a JavaScript shell) and extracts the content. Calls are answered free when the fetch is free — a plain fetch inside the daily allowance, or a cache hit inside the free cache allowance. When serving the page would require payment (x402, USDC on Base), the call returns an error directing you to the paid HTTP API at POST https://backfill.top/v1/fetch; payment is never attempted over MCP.
Inputs: url (required), mode.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Pay-per-call web reader (Markdown/RAG chunks) and agent utilities; x402 USDC on Base.
Pay-per-request webpage-to-Markdown extraction for AI agents. $0.005 USDC via x402 on Solana.
Pay-per-call web tools for agents (extract, summarize, ask, JSON) via x402 USDC on Base.
Pay-per-call website checks, web fetch and data tools for AI agents (x402, USDC on Base).
Related MCP Servers
- AlicenseAqualityCmaintenancePay-per-use clean web reader for AI agents. URL in, markdown plus metadata out, in milliseconds. Settled per-call in USDC over x402 — no signup, no API keys.1102 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to convert any URL into clean, structured, agent-optimized content with a single paid call, paying $0.02 USDC per successful extraction via x402 on Base without API keys or accounts.MIT
- AlicenseAqualityBmaintenanceGives AI agents web pages as clean Markdown, links, metadata or JSON that follows your schema. Each call is paid in USDC on Base via x402 ($0.002-$0.02), with built-in spending limits.121,162 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables extracting clean Markdown from any webpage by paying $0.005 USDC per call via the x402 protocol, with automatic wallet-based payment settlement.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.