Skip to main content
Glama
Dempty-glitch

Z-ZERO MCP

by Dempty-glitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Z-ZERO MCP

No user-submitted related servers found.

    Related Servers

    • veyra-mcp

      zapxlabs
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to make non-custodial USDC payments on Base through an MCP endpoint, with server-enforced per-payment and daily caps, human approval bands, and recipient allowlists.
      7
      354 npm
      MIT

    • 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
      1
      MIT

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT

    • xpay

      xona-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      415 npm
      1
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools overlap in the payment flow (auto_pay_checkout, request_payment_token, execute_payment) and balance retrieval (list_cards vs check_balance), though detailed descriptions provide usage guidance. The boundaries are not always immediately clear, but the added context reduces misselection risk.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., list_cards, request_payment_token). There is no mixing of styles or unexpected abbreviations.

    Tool Count5/5

    13 tools is well within the typical 3-15 range and each tool serves a clear function in the payment lifecycle. The count feels appropriate for the server's scope.

    Completeness4/5

    The tool surface covers the full workflow from deposit and card creation to payment execution and receipt verification. Minor gaps like a transaction history or explicit refund initiation exist, but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources