io.github.FieldmodeLLC/scrapecheck
REMOTE · SCRAPECHECK-MCP.FLY.DEV · SCANNED SEP 20
Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 634 tokens (~211/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.FieldmodeLLC/scrapecheck MCP server?
io.github.FieldmodeLLC/scrapecheck is a hosted endpoint at https://scrapecheck-mcp.fly.dev/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 · scrapecheck-mcp.fly.dev
claude mcp add --transport http fieldmodellc-scrapecheck 'https://scrapecheck-mcp.fly.dev/mcp'
{
"mcpServers": {
"fieldmodellc-scrapecheck": {
"url": "https://scrapecheck-mcp.fly.dev/mcp"
}
}
} {
"servers": {
"fieldmodellc-scrapecheck": {
"type": "http",
"url": "https://scrapecheck-mcp.fly.dev/mcp"
}
}
} [mcp_servers.fieldmodellc-scrapecheck] url = "https://scrapecheck-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fieldmodellc-scrapecheck": {
"type": "remote",
"url": "https://scrapecheck-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add fieldmodellc-scrapecheck --url 'https://scrapecheck-mcp.fly.dev/mcp' --transport streamable-http
mcp_servers:
fieldmodellc-scrapecheck:
url: "https://scrapecheck-mcp.fly.dev/mcp" {
"McpServers": {
"fieldmodellc-scrapecheck": {
"Transport": "http",
"Url": "https://scrapecheck-mcp.fly.dev/mcp"
}
}
} assistant mcp add fieldmodellc-scrapecheck -t streamable-http -u 'https://scrapecheck-mcp.fly.dev/mcp'
{
"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.
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.
- 15 Sept 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 14 Sept 26 −7
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 10 Sept 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 6 Sept 26 −7
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 5 Sept 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 4 Sept 26 −7
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 31 Aug 26 +7
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Stability: 0.97 → pass security
- 30 Aug 26 −6
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
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 20 Sept 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=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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 →
get_verifier_info Verifier trust info (free) ~82
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_presence Presence check (not an answer check) ~230
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.
| 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 | – |
| key_id | string | – | – |
| reasons | array | yes | – |
| signature | string | yes | – |
| source_hash | string|null | – | – |
| verdict | string | yes | – |
| verdict_id | string | yes | – |
| verifier_url | string | – | – |
No examples provided.
verify_web_field Verify scraped claim (full) ~322
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.
| 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 | – |
| key_id | string | – | – |
| reasons | array | yes | – |
| signature | string | yes | – |
| source_hash | string|null | – | – |
| verdict | string | yes | – |
| verdict_id | string | yes | – |
| verifier_url | string | – | – |
No examples provided.
What is the io.github.FieldmodeLLC/scrapecheck MCP server?
io.github.FieldmodeLLC/scrapecheck is an MCP server listed in the public MCP registry as io.github.FieldmodeLLC/scrapecheck. Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402. This page covers its hosted endpoint (https://scrapecheck-mcp.fly.dev/mcp).
Is the io.github.FieldmodeLLC/scrapecheck MCP server safe to use?
io.github.FieldmodeLLC/scrapecheck scores 85 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 io.github.FieldmodeLLC/scrapecheck MCP server expose?
io.github.FieldmodeLLC/scrapecheck exposes 3 tools: verify_web_field, verify_presence, get_verifier_info. Their descriptions and schemas cost roughly 634 tokens of context every time the server is loaded.
Does the io.github.FieldmodeLLC/scrapecheck MCP server require authentication?
No. We connected to io.github.FieldmodeLLC/scrapecheck without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.FieldmodeLLC/scrapecheck MCP server still maintained?
io.github.FieldmodeLLC/scrapecheck is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.