Skip to main content
Glama
m2mmonster

m2m-monster

Official
by m2mmonster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to m2m-monster

No user-submitted related servers found.

    Related Servers

    • solinkify-mcp

      Zenidp
      A
      license
      A
      quality
      C
      maintenance
      Agentic payments on Solana: an agent can pay x402 / HTTP 402 paywalls in USDC, hold a pre-paid balance or a subscription, and buy datasets or settle store checkouts. All 15 tools run behind fail-closed spending caps ($1 per payment, $10 per day by default), and settlement is non-custodial through a program-owned escrow that releases 99% to the creator.
      18
      35 npm
      MIT

    • AgentWallet MCP Server

      hifriendbot
      A
      license
      B
      quality
      B
      maintenance
      Provides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.
      40
      288 npm
      3
      MIT
    • PipRail by piprail

      PipRailofficial

      piprail
      A
      license
      A
      quality
      A
      maintenance
      A budget-bound x402 payment wallet for AI agents: it autonomously pays HTTP 402 payment-gated URLs across every major chain (EVM, Solana, and many non-EVM families). Self-custodial and backendless, your key, your RPC, with spend caps enforced before any on-chain send.
      8
      9
      MIT

    • obol

      halfkey
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to access Solana wallet analytics, token data, and DeFi tools via pay-per-request USDC micropayments using the x402 protocol, without API keys or subscriptions.
      13
      19 npm
      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.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    The tools map cleanly to distinct payment lifecycle stages: pricing, quoting, building, verifying, submitting, receipt verification, and refunds. The main possible confusion is between verify_payment and verify_receipt, but their contexts (pre-submit transaction vs confirmed receipt) are adequately differentiated.

    Naming Consistency5/5

    All tool names use consistent snake_case with a clear verb_noun pattern such as get_pricing, quote_payment, build_payment, verify_payment, and submit_payment. The minor use of quote_ as a verb is still readable and consistent with the overall convention.

    Tool Count5/5

    Ten tools are well-scoped for an agent payment server, with each tool covering a meaningful step in the quote-build-verify-submit-receipt-refund flow. Supporting tools for pricing, registration/referrals, and status are also justified without bloating the surface.

    Completeness4/5

    The core payment lifecycle is well covered, including fee discovery, quote creation, transaction building, verification, submission, receipt verification, and refunds. Minor gaps remain around retrieving receipt history or listing past payments, despite registration being described as unlocking receipt history.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources