Skip to main content
Glama
mandalito

StealthPay MCP

by mandalito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to StealthPay MCP

No user-submitted related servers found.

    Related Servers

    • Cerberus

      lz-123123
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a three-layer payment firewall for AI agents, enabling identity verification, risk screening, and execution authorization with on-chain policy enforcement for secure and auditable transactions.
      213 npm
      2
      MIT

    • remit.md MCP Server

      pay-skill
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      3 npm
      MIT

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

    • BotWallet MCP Server

      botwallet-co
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.
      36
      8 npm
      4
      Apache 2.0
    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.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose, covering separate actions like generating addresses, sending payments, managing ENS names, resolving profiles, creating payment links, and claiming funds. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern with hyphens (e.g., generate-stealth-address, send-stealth-payment). The naming is predictable and uniform throughout the set.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its privacy-focused payment domain. Each tool is essential and covers key operations without unnecessary bloat or missing core functionality.

    Completeness3/5

    The tool surface covers most of the stealth payment workflow, but a critical tool for scanning announcements (as referenced in claim-stealth-payment) is missing, creating a dependency on external inputs. Additionally, no tools for balance checks or transaction history are provided.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources