Skip to main content
Glama
Sign In
x402-pilot

x402-pilot

by DrVelvetFog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to x402-pilot

No user-submitted related servers found.

    Related Servers

    • x402lint

      arden-instance
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and IDE assistants to validate x402 payment endpoints without shelling out: it fetches a URL unpaid and returns a conformance report on the returned 402 challenge, decodes and classifies base64 payment blobs, and summarises which scheme/network pairs a facilitator can settle.
      MIT

    • provenpaid-mcp

      justinsmithphd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to validate x402 endpoints and review on-chain payment evidence before relying on them, with free initial checks and automated USDC payments under configurable safety limits.
      35 PyPI
      MIT

    • x402lint

      something-agent
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables linting the unpaid path of an x402 endpoint by fetching a paid URL or inspecting a payment-required challenge you already hold, returning a verdict with severity-tagged findings, fixes, and a list of what went untested. Checks challenge fields, transport behavior, and discovery documents without ever signing or paying.
      2 npm
      MIT

    • x402 Preflight

      chico10117
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents to inspect and audit unfamiliar x402 endpoints before spending USDC, using bounded read-only probes to surface payment challenges, pricing, network, receiver, and operational signals without signing or spending funds.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct artifact: PaymentRequired decoding, PAYMENT-RESPONSE inspection, code compliance scanning, spec linting, extension validation, and end-to-end conformance runs. The decode_402 vs inspect_payment_response pair could be momentarily confused, but descriptions clearly split request-side vs response-side, and run_conformance is clearly an orchestrator over the others.

    Naming Consistency4/5

    All tools follow a consistent snake_case verb_noun pattern (check_compliance, lint_scheme_spec, validate_extension, run_conformance). decode_402 is the only minor deviation, embedding a number instead of a noun, but it remains readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for an x402 validation/compliance toolkit, with each tool covering a distinct stage of the protocol surface. No bloat and no obviously missing companion tool given the read-only, no-keys design.

    Completeness4/5

    The surface covers parsing 402 requests, inspecting responses with on-chain recomputation, spec linting, extension validation, code compliance, and conformance sequencing—a broad lifecycle. Minor gaps exist (no payment construction/signing), but that omission is deliberate given the server holds no keys.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources