Skip to main content
Glama

Related Servers

Alternatives to ScrapeCheck MCP

  • F
    license
    Not graded
    quality
    C
    maintenance
    A 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.
    -
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP 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

  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP 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.
    298 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP 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
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that provides live fair-market-value price comparisons and Ed25519 signed-receipt verification for x402/MPP services, enabling agents to sanity-check quotes and verify receipts.
    40
    Apache 2.0

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
ResponsivenessNo issues