mcpbeat Sign in

Backfill Fetch MCP Server

answering

Backfill Fetch is answering right now. Last checked 5 min ago. It exposes 2 tools.

Pay-per-fetch web extraction for agents: POST a URL, get clean markdown. x402 USDC on Base.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
146 ms
Response time
average over 24h
open, no key
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add backfill-fetch --transport http https://backfill.top/mcp
Settings → Connectors → Add custom connector, then paste this address
https://backfill.top/mcp
~/.codex/config.toml
[mcp_servers.backfill-fetch]
url = "https://backfill.top/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "backfill-fetch": {
      "url": "https://backfill.top/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "backfill-fetch": {
      "type": "http",
      "url": "https://backfill.top/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

extract
extract_data
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.
page
fetch_page
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.

Endpoints

URLTransportStateLatencyChecked
https://backfill.top/mcp streamable-http answering 122 ms 5 min ago

Alternatives to Backfill Fetch

same job, measured the same way
Avo Cado Read
by workers-a-347-avocado-read-api

Web page to clean Markdown for agents. Pay per call ($0.003 USDC on Base) via x402.

2 tools answering
AgentPay Web Extract
by noah-silver

Pay-per-call web page to markdown, metadata and links for agents. x402 USDC on Base or Algorand.

1 tools answering
AgentRead
by omarhassanatef

Web pages to clean Markdown for AI agents. 5 free calls/day, then pay per call via x402 on Base.

3 tools answering
1gateway
by code0xff

Pay-per-call tools for agents via x402 (USDC on Base): Korean data, doc-to-Markdown, web utilities.

121 tools answering
gofetch
by getgofetch

Web page to JSON fields (by JSON Schema) for agents. Pay per call in USDC on Base via x402.

2 tools answering
x402 Web Tools
by iparadise71

Pay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC)

4 tools answering
X
x402 Markdown Reader
by workers-xbtbot-x402-reader

Turn any public web page into clean Markdown. Pay-per-call via x402: 0.005 USDC on Base.

2 tools answering
Orchard Data MCP
by letom1176-spec

Pay-per-call market data for AI agents via x402 (USDC on Base): regime, track record, catalysts.

127 installs/wk local only

Backfill Fetch — questions

Answers built from our own checks of this server.

What can Backfill Fetch do?
It exposes 2 tools, read directly from the server on our last check. Among them: extract_data, fetch_page. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Backfill Fetch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 146 ms. The bar chart above shows every period we have measured.
Is Backfill Fetch still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Backfill Fetch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Backfill Fetch need an API key?
No. Backfill Fetch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Backfill Fetch?
It answers our handshake in 146 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.