Skip to main content
Glama
route-verdict-mcp

route-verdict-mcp

Related Servers

Alternatives to route-verdict-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to run read-only trust checks on an x402 endpoint and receive a signed report covering endpoint lint, signed offers, ERC-8004 identity, and payer mix before paying.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP host to run an automated, non-destructive security audit of a paid x402 endpoint URL and receive a SECURE/FINDINGS/EXPOSED verdict with per-check evidence. The built-in tool handles the entire x402 payment flow — challenge, signed USDC authorization on Base, paid retry — using the user's own wallet, with a spend guard.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run full on-page SEO audits for any URL or up to 10 URLs at once, returning 0-100 scores, meta tag and heading checks, schema/image/link analysis, load time, and prioritized fixes via pay-per-call x402 micropayments.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to obtain an independent review of their drafts, returning a pass/fail verdict with specific issues and suggested fixes, plus a signed receipt. Payments are made per check over x402, with no account or API key needed.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and systems to look up an agent endpoint URL and receive a machine-readable trust decision — reliability evidence, endpoint ownership verification, confidence, and reasons — before deciding whether to interact with it. Lookups are read-only, require no API key, and never contact the target endpoint during the check.
      MIT

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With a single tool there is no possibility of confusion or misselection. The purpose (audit an x402 endpoint before paying) is clearly articulated and distinct from anything else in the surface.

    Naming Consistency5/5

    The lone tool, route_check, follows a clean verb_noun (domain_verb) pattern that is readable and predictable. There are no competing conventions to clash with.

    Tool Count3/5

    One tool is thin for a server, even a narrowly scoped one; it maps to a single paid endpoint, so a minimal surface is defensible, but agents have no complementary operations (e.g. batch check, fetch cached verdict without paying) to work with.

    Completeness4/5

    The tool returns a rich, self-contained result (verdict, score, deductions, live probe, terms, catalog presence, diff vs. last check), which covers the core audit workflow well. Minor gaps exist: no way to retrieve a prior verdict without a new paid call, and no batch or list operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues