Skip to main content
Glama
zapxlabs

veyra-mcp

by zapxlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to veyra-mcp

No user-submitted related servers found.

    Related Servers

    • Z-ZERO MCP

      Dempty-glitch
      A
      license
      A
      quality
      B
      maintenance
      Payment infrastructure MCP server enabling AI agents to make gasless USDC payments on Base and JIT single-use virtual card checkouts, with zero-trust card handling, merchant checkout hints, and signed receipts.
      13
      602 npm
      1
      MIT

    • ARCANUM plugin for PayBox

      bunnyyxtan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create and manage contract-guarded USDC wallets on Base with enforceable per-payment, daily, and monthly caps, vendor allowlists, escalation thresholds, and freeze controls. It provides read-only policy checks plus unsigned transaction proposals for payments, funding, vendor management, wallet creation, and module deployment without holding keys or broadcasting.
      Apache 2.0

    • Boundra

      gobeyondfj-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to evaluate every payment intent against user-signed, on-chain-anchored policies before money moves, returning allow, deny, or human-approval verdicts. Provides policy versioning, revocation, spend reports, and audit trails through MCP tools that agents cannot alter without the owner's key.
      1
      Apache 2.0

    • pay-mcp

      MonadWorks
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for USDC payments on Base, enabling AI agents to check balances, send payments, generate payment requests, and view transaction history.
      4
      2
      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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct action or resource: capabilities, budget, payment sources, and individual payments are clearly separated. The only mild overlap is between get_capabilities and get_budget, since both surface policy/limit information, but their focuses are distinct enough to avoid real confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: get_, list_, create_, cancel_. Reading operations consistently use get_ for single resources and list_ for collections, making the naming predictable and easy to navigate.

    Tool Count5/5

    Seven tools is well-scoped for a payment-focused server. Each tool covers a necessary part of the payment lifecycle or policy context without unnecessary duplication or bloat.

    Completeness5/5

    The surface covers the full agent-relevant payment workflow: discover capabilities, check budget, list payment sources, create a payment, retrieve one payment, list past payments, and cancel when possible. There are no obvious dead ends or missing core operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources