F
licenseNot graded
qualityD
maintenanceA remote MCP server that verifies paid x402 and MCP tools for discoverability, inspectability, and claim-bound correctness, enabling pre-submission readiness checks for agent-tool sellers.
-
ScrapeCheck MCP
Officialby FieldmodeLLC
Related Servers
Alternatives to ScrapeCheck MCP
- FlicenseNot gradedqualityBmaintenanceMCP server for creating cryptographically signed and timestamped evidence of public web/API responses, with offline verification of attestations and paid access via x402.-
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that checks an x402 paid endpoint before an agent pays it, and checks afterwards that the receipt opens to exactly one real on-chain settlement. Two tools, no account, no API key.1,498 npmApache 2.0
fetcher.cloudofficial
AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents web capabilities such as rendering pages, extracting content, resolving links, and inspecting domains, with per-call USDC payments via x402.MIT- AlicenseAqualityBmaintenanceA paid MCP server that extracts structured product data (schema.org/Product) from any URL via headless browser, charging $0.01 USDC per call through x402 micropayments.112 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents scrape web pages as clean markdown for a micro-payment in USDC, using the x402 protocol on Base network. No API keys or signup required.MIT
@clawfetch/mcpofficial
AlicenseNot gradedqualityAmaintenanceMCP server providing web intelligence tools for AI agents, including fetching pages as markdown, rendering JS-heavy SPAs, extracting structured data, multi-source research, and domain availability checks, with automatic x402 micropayments.25 npmMIT- AlicenseNot gradedqualityCmaintenanceMCP server providing 10 pay-per-call APIs for web scraping, DNS, email validation, and French business data, with autonomous micropayments via the x402 protocol (USDC on Base).MIT
TDQS
A4.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: the full verification check, the cheaper presence-only check, and the free verifier-info endpoint. The descriptions explicitly contrast verify_web_field and verify_presence, eliminating any ambiguity about which to call.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: verify_web_field, verify_presence, get_verifier_info. The verbs (verify/get) are semantically appropriate and predictable.
Tool Count5/5
Exactly three tools cover a narrow, focused purpose: two verification paths and one supporting key-info endpoint. Nothing feels redundant or missing at this scope.
Completeness5/5
The surface covers the full verification workflow: a precise check, a cheaper screening check, and offline verifiability via the public key. The stated scope (server-rendered pages) is respected and no obvious dead ends exist.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive