Skip to main content
Glama
agenticpay-dev

agenticpay

by agenticpay-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agenticpay

No user-submitted related servers found.

    Related Servers

    • payclaw

      TeaBay
      A
      license
      Not graded
      quality
      B
      maintenance
      Drop-in x402 payment middleware for MCP servers. Charge AI agents per tool call using USDC on Base chain — Python and JavaScript SDKs, no payment processor, no KYC.
      MIT

    • solinkify-mcp

      Zenidp
      A
      license
      A
      quality
      A
      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
      92 npm
      MIT

    • PayGate MCP

      geoacpfilho
      A
      license
      Not graded
      quality
      B
      maintenance
      Monetization gateway for MCP servers, enabling pay-per-call AI agent access with x402 payment challenges and USDC settlement on Base. Developers can register existing MCP servers, set tool prices, and receive payments without handling payment code.
      90 npm
      MIT

    • @melis-ai/x402-tools-mcp

      mizukaizen
      A
      license
      B
      quality
      D
      maintenance
      An MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.
      17
      89 npm
      1
      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

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no ambiguity between tools.

    Naming Consistency5/5

    With a single tool, naming is trivially consistent; the name uses a clear verb_noun pattern.

    Tool Count1/5

    One placeholder tool is far too few for a server named 'agenticpay', which implies a payment domain requiring multiple operations.

    Completeness1/5

    The server lacks any functional tools; a payment server should have tools for transactions, balances, etc., but there is only a placeholder.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources