Pay-per-fetch web extraction for agents: POST a URL, get clean markdown. x402 USDC on Base.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
A JSON Schema object describing the data to extract
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http backfill-fetch https://backfill.top/mcp
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.
| Argument | Type | Description |
|---|---|---|
| url* | string | |
| mode | string | |
| schema* | object | A JSON Schema object describing the data to extract |
{
"type": "object",
"required": [
"url",
"schema"
],
"properties": {
"url": {
"type": "string"
},
"mode": {
"enum": [
"auto",
"plain",
"render"
],
"type": "string",
"default": "auto"
},
"schema": {
"type": "object",
"description": "A JSON Schema object describing the data to extract"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| url* | string | |
| mode | string |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string"
},
"mode": {
"enum": [
"auto",
"plain",
"render"
],
"type": "string",
"default": "auto"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 2, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.