MCP.Market

Scrapecheck MCP server

online · 96% uptime
by FieldmodeLLC·io.github.FieldmodeLLC/scrapecheck·v0.2.1

Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Scrapecheck yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Scrapecheck tools (3)

write = sends, deletes, buys or posts
  • get_verifier_infoFree

    Free. Returns the public key, engine version, benchmark summary with sample-size labels, and scope, so you can verify any verdict offline. Call this first if your selection policy requires evidence before trusting a verification provider: every verdict this service issues verifies offline against the returned key, so you do not have to trust the service at runtime to rely on its output.

  • verify_presenceFree

    Presence only: confirms the value appears on the page, NOT that it is the right answer to what was asked. Never returns pass. A was-price, a different variant's price, a shipping cost, or a tax figure can all satisfy presence. Verdicts are present, fail, or unverifiable, signed, with check_type web_field_presence_v1. Use it as a cheap screen before a full check, or when you already know what the value means and only need to confirm it still appears on the page. If your decision depends on the value being the right value, call verify_web_field instead. Scope: server-rendered pages. $0.002 per check, paid in-band via x402.

  • verify_web_fieldFree

    Checks whether a value you did not fetch yourself is actually on the source page right now, and returns a signed pass/fail/unverifiable verdict. Not a retrieval tool: it checks a value you already have, it does not find data for you. Use it when you hold a value that came from somewhere else (a search result, a scraper, an upstream API, another agent) and you need to know it is on the source page before you act on it. Takes the URL, the claimed value, and what was asked; it independently re-fetches the page and never trusts the fetch you were given. Structural guarantee: a claim is never certified unless the re-fetched page contains it, and the model judge can only veto a pass, never create one. Anything unconfirmed returns unverifiable, never pass. Every verdict carries a stable verdict_id, the engine digest that produced it, and a signature verifiable offline against the public key (see get_verifier_info). Scope: server-rendered pages; JS-only content returns unverifiable rather than a guess. $0.01 per check, first 100 free, paid in-band via x402.

Public scan report

scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1019ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Scrapecheck compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 80% of 4,460 AI and agents servers
Tools
3
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
96%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
111 ms
faster than 84% of 2,331 AI and agents servers

What its tools let an agent do: 3 read

Install Scrapecheck in Claude Code, Cursor or VS Code

claude mcp add --transport http scrapecheck https://scrapecheck-mcp.fly.dev/mcp
Add to Cursor

What the publisher says

From the Scrapecheck repository's README, as published. We do not edit it. Read it on GitHub

ScrapeCheck MCP: the verification beat for agents that spend

Here for the offline verifier? It's in this repo:

tools/verify-verdict.mjs — one file, no

dependencies, verifies any ScrapeCheck verdict with no network access.

How to use it →

Agents now find a provider, pay through x402, receive data, and act on it. Nothing in that flow asks whether the data is true. This server adds the missing beat. Before your agent acts on a value it fetched or paid for, it sends the source URL, the value, and what was asked; ScrapeCheck re-fetches the page from its own infrastructure and returns an ed25519-signed verdict: pass, fail, or unverifiable. Never a guess, and anything unconfirmed is unverifiable, never pass.

One line to install, and the agent pays per check through the same x402 rail it already spends on: no API key, no signup, a free allowance before payment is required, and every verdict verifiable offline against our published key.

Want to see a verdict before installing anything? One free check runs in the browser at scrapecheck.fly.dev.

All four integration lanes (MCP, x402-native, Apify, plain HTTP), each with a tested snippet: scrapecheck.fly.dev/integrations

Endpoint: https://scrapecheck-mcp.fly.dev/mcp (streamable HTTP) Payment: x402 in-band (USDC on Base) — no API key, no signup. A free allowance per client identity is served before payment is required.

Check us yourself — the three things you can attack: verify any verdict offline · live run stats, misses included · the benchmark and its limits

Tools

  • verifywebfield — $0.01 — Full verification: value present on the re-fetched live page, served live, and an independent LLM judge confirms it answers what was asked. Positive verdict: pass.
  • verifypresence — $0.002 — Presence only — does NOT** confirm the value answers the question. Positive verdict: present, never pass.
  • getverifierinfo — free — The trust artifact: public key, benchmark summary, scope, endpoints.

Where this sits in an agent's spending loop

The payment rail answers who paid what, on whose authority. The receipt is perfect, and the receipt holds no evidence about the data. This tool is the step between receiving and acting: one call per value your agent is about to trust, priced in the same cents the data itself cost.

The trust guarantee is structural, not statistical

A claim is never certified unless ScrapeCheck independently re-fetches the page and finds the claimed value there itself — and the judge's vote is mechanically voided if its restatement of the claim doesn't match what was actually claimed. Absence cannot pass, and substitution cannot pass. Anything unconfirmed — a skipped check, a failed fetch, a judge that errors — returns unverifiable, never pass.

Corroborated by benchmark (full verification only): 0 false passes across 67 frozen labeled cases (26 held out from all calibration, including adversarial traps where the claimed value appears on the page as the wrong thing), and 0 false passes across 21 live-web cases including 9 adversarial traps. Small-N corroboration of the structural guards — not a population accuracy claim.

Why trust this server's own claims?

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Scrapecheck: common questions

Is Scrapecheck MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Scrapecheck safety report
How do I install Scrapecheck?
It runs remotely at scrapecheck-mcp.fly.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Scrapecheck need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Scrapecheck maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.2.1.
Is Scrapecheck up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Scrapecheck?
Servers from other publishers that do the same job: Emilia Protocol MCP server, Decionis MCP server and Watch Skill MCP server.
How does Scrapecheck compare with other AI and agents MCP servers?
safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 3 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Scrapecheck

Same job from other publishers: the closest match first, then the best rated.

  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • three.ws 3D Agent Tools
    MCP tools from three.ws: free + paid text-to-3D, rigging, agent reputation, market intel.
    B