Backfill Fetch
REMOTE · BACKFILL.TOP
Pay-per-fetch web extraction for agents: POST a URL, get clean markdown. x402 USDC on Base.
Available components
Last scanned (1 hour ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 310 tokens (~155/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://backfill.top/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=backfill.top | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7e7aada605d7bc800e3869444308616e |
| SANs: backfill.top, *.backfill.top | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of backfill.top. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| top. | present | 41508 | 13 | Verified |
| backfill.top. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://backfill.top/mcp | Verified | 200 | |
| http (plaintext) | http://backfill.top/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
extract_data ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| schema | object | yes | A JSON Schema object describing the data to extract |
| url | string | yes | – |
No output schema declared.
No examples provided.
fetch_page ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Backfill Fetch MCP server?
Backfill Fetch is a hosted endpoint at https://backfill.top/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · backfill.top
claude mcp add --transport http top-backfill-backfill-fetch 'https://backfill.top/mcp'
What is the Backfill Fetch MCP server?
Backfill Fetch is an MCP server listed in the public MCP registry as top.backfill/backfill-fetch. Pay-per-fetch web extraction for agents: POST a URL, get clean markdown. x402 USDC on Base. This page covers its hosted endpoint (https://backfill.top/mcp).
Is the Backfill Fetch MCP server safe to use?
Backfill Fetch scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Backfill Fetch MCP server expose?
Backfill Fetch exposes 2 tools: fetch_page, extract_data. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.
Does the Backfill Fetch MCP server require authentication?
No. We connected to Backfill Fetch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Backfill Fetch MCP server still maintained?
Backfill Fetch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.