Skip to main content
Glama
Sign In
AgentPay MCP Server

AgentPay MCP Server

by yyxqqq777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AgentPay MCP Server

No user-submitted related servers found.

    Related Servers

    • PayAgent

      Evoarislan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to autonomously pay for metered web APIs on a per-call basis, settling x402 v2 USDC micropayments via EIP-3009 authorization on Base Sepolia without human involvement. Spending is bounded by configurable per-call caps and host restrictions, and exposes tools to fetch paywalled URLs and inspect the agent wallet's address and balance.
      MIT

    • x402-firewall

      x402-firewall
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to securely access x402-protected APIs on Base L2 with automatic USDC payments under deterministic spending limits, domain and contract allowlists, transaction simulation, and audit logging.
      4
      764 npm
      MIT
    • @bridgenode/mcp

      @bridgenode/mcpofficial

      bridgenode-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to make pay-as-you-go AI inference requests through x402 with automatic Solana USDC payments, no API keys or registration, while enforcing configurable spending limits.
      3
      196 npm
      1
      MIT No Attribution

    • agent-x402

      rustemmustafingovua-byte
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to check their wallet address and USDC balance, preview the cost of an x402 call, and pay for API requests in USDC on Base without an account or API key. Spend caps, allow-lists and blocked contracts are enforced in code before anything is signed, so a prompt injection cannot bypass them.
      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.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: payment status check, wholesale pricing search, XHS note detail, and XHS user note listing. The two XHS tools are complementary (single item vs. list) rather than overlapping, so an agent can disambiguate easily.

    Naming Consistency2/5

    Names mix conventions: `agentpay_payment_status` and `china_wholesale_pricing_query` are noun-heavy and lack a clear verb, while `xhs_get_note_detail` and `xhs_get_user_notes` follow a get_object pattern. The shared prefixes are helpful, but the action verbs are inconsistent and not uniformly placed.

    Tool Count3/5

    4 tools is at the low end of a reasonable count. The number is not problematic by itself, but it spans several unrelated domains (payment, China wholesale, Xiaohongshu), making the set feel like a small fragment of a broader service rather than a cohesive server.

    Completeness2/5

    The payment domain is represented only by a status check, and the data tools each provide one narrow read operation: wholesale has only a search, and XHS lacks obvious endpoints like search by keyword or fetching user profile/context. This leaves common workflows with no corresponding tool on the server.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources