Skip to main content
Glama
Sign In
Lumière PayCheck

Lumière PayCheck

by Book0fEli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Lumière PayCheck

No user-submitted related servers found.

    Related Servers

    • 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.
      18 PyPI
      MIT

    • crest-verify

      andysalvo
      A
      license
      Not graded
      quality
      D
      maintenance
      Verify x402 endpoints before your agent spends. Three tools: verify (SPEND/CAUTION/INVESTIGATE/DO NOT SPEND backed by 50K+ services), passport (full trust identity), risk_check (deep assessment). No API keys, no signup.
      12 npm
      MIT

    • ada-wallet

      loveaihq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.
      329 npm
      Apache 2.0

    • tryx402

      crypto-yannso
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover and safely call any x402/AgentCash pay-per-call endpoint with hard budget caps, idempotency keys, spend ledgers, pre-flight cost estimation, and offline-verifiable signed receipts. Exposes search, discovery, paid-call, spend, plan, and receipt tools, plus optional hosted-account balance, recharge, and proxy tools.
      MIT
    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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, and the descriptions explicitly cross-reference each other (check_endpoint vs check_payment vs top_endpoints, etc.) to route the agent correctly. check_endpoint for one endpoint, check_payment before paying, top_endpoints for discovery, catalog_stats for aggregate, report_outcome for post-payment, get_full_report for paid deep-dive — no meaningful overlap.

    Naming Consistency4/5

    Four tools follow a clean verb_noun pattern (check_endpoint, check_payment, report_outcome, get_full_report) with snake_case throughout. top_endpoints and catalog_stats are noun-phrase/collections, a minor deviation from the verb-led convention but still readable and predictable.

    Tool Count5/5

    Six tools is well-scoped for an endpoint-trust service, with each tool earning its place across discovery, single-endpoint checking, payment gating, reporting, and catalog context. No redundancy or padding.

    Completeness4/5

    The surface covers the lifecycle: discovery (top_endpoints), inspection (check_endpoint), payment approval (check_payment), feedback (report_outcome), context (catalog_stats), and paid deep-dive (get_full_report). Minor gaps remain — batch grading, wallet-risk, and watch alerts are only advertised as paid x402 endpoints rather than exposed as MCP tools, and there's no direct free history retrieval.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources