io.github.FieldmodeLLC/scrapecheck

REMOTE · SCRAPECHECK-MCP.FLY.DEV · SCANNED AUG 3

Verify scraped data against the live source page. Signed verdicts, $0.01 via x402.

Available components

62 62 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security57

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 3 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 is enforced; there's no plaintext access path. View diagnostics → Pass
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 Usability68

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 580 tokens (~193/item across 3 items; 3 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 Management7

Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · scrapecheck-mcp.fly.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http fieldmodellc-scrapecheck https://scrapecheck-mcp.fly.dev/mcp

# ~/.codex/config.toml

[mcp_servers.fieldmodellc-scrapecheck]
url = "https://scrapecheck-mcp.fly.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fieldmodellc-scrapecheck": {
      "type": "remote",
      "url": "https://scrapecheck-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add fieldmodellc-scrapecheck --url https://scrapecheck-mcp.fly.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  fieldmodellc-scrapecheck:
    url: "https://scrapecheck-mcp.fly.dev/mcp"

// mcp.json

{
  "mcpServers": {
    "fieldmodellc-scrapecheck": {
      "type": "http",
      "url": "https://scrapecheck-mcp.fly.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +10
- HSTS header: unverified → fail ▼ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
2 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
1 Aug 26 51

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://scrapecheck-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.fly.dev	CN=YE2,O=Let's Encrypt,C=US	21 Jun 2026	19 Sept 2026	ECDSA 256	ECDSA-SHA384	503153e73302e4a0c89ebb83c4a741aac04
SANs: *.fly.dev
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of scrapecheck-mcp.fly.dev. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
dev.	present	60074	8	Verified
fly.dev.	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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://scrapecheck-mcp.fly.dev/mcp	Verified	200
http (plaintext)	http://scrapecheck-mcp.fly.dev/mcp	HTTPS enforced	301	https://scrapecheck-mcp.fly.dev/mcp

MCP tools — 3 exposed · ~580 tokens

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.

Tool Tokens

get_verifier_info Verifier trust info (free) ~77

Free trust artifact: the evidence for deciding whether to trust ScrapeCheck's verdicts, in-band. Returns the ed25519 public key every verdict signature verifies against, the benchmark summary with honest small-N labels, the scope statement, and service endpoints. Verdicts are signed over canonical sorted-key JSON of all fields except "signature".

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verify_presence Presence check (not an answer check) ~212

Presence check only — this does NOT confirm the value is the right answer to what was asked, and its positive verdict is "present", never "pass". It confirms the claimed value appears on the live source page: ScrapeCheck independently re-fetches the URL and checks the value is present and served live, with no LLM judge. Published accuracy numbers apply to full verification (verify_web_field) only. Returns a signed verdict ("present", "fail", or "unverifiable") with check_type "web_field_presence_v1". Scope: server-rendered pages. $0.002 per call via x402.

Input Output Examples

Name	Type	Req	Description
asked	string	yes	What the scraper was asked to extract, e.g. "get the current price and stock status"
claim	object	yes	The scraped field(s) to verify against the live page, e.g. {"price": "£51.77", "in_stock": true}
url	string	yes	URL of the source page the claim was scraped from

Name	Type	Req	Description
check_type	string	yes	—
confidence	number	yes	—
engine	string	yes	—
evidence	object	yes	—
reasons	array	yes	—
signature	string	yes	—
verdict	string	yes	—
verdict_id	string	yes	—

No examples provided.

verify_web_field Verify scraped claim (full) ~291

Verify a scraped claim against the live source page and get back an ed25519-signed verdict: "pass", "fail", or "unverifiable". ScrapeCheck independently re-fetches the URL itself, confirms the claimed value is actually present and served live (not a stale cache), and an independent LLM judge confirms the value answers what was asked. The guarantee is structural, not statistical: a claim is never certified unless the re-fetched page contains it, AND a judge's vote is mechanically voided if its restatement of the claim doesn't match what was actually claimed — absence cannot pass, substitution cannot pass, and 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; client-rendered (JS-only) content returns "unverifiable". $0.01 per call via x402.

Input Output Examples

Name	Type	Req	Description
asked	string	yes	What the scraper was asked to extract, e.g. "get the current price and stock status"
claim	object	yes	The scraped field(s) to verify against the live page, e.g. {"price": "£51.77", "in_stock": true}
url	string	yes	URL of the source page the claim was scraped from

Name	Type	Req	Description
check_type	string	yes	—
confidence	number	yes	—
engine	string	yes	—
evidence	object	yes	—
reasons	array	yes	—
signature	string	yes	—
verdict	string	yes	—
verdict_id	string	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug