Skip to main content
Glama
Irohitjain

AgentPay Pharos

by Irohitjain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AgentPay Pharos

No user-submitted related servers found.

    Related Servers

    • automaton-onchain-tools

      povrouyre-wq
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access pay-per-call onchain and URL safety APIs over MCP, covering transaction explanations, token approval checks, address inspection, contract risk heuristics, URL safety, gas snapshots, ENS resolution, calldata decoding, and wallet portfolio data. Payments are handled per call in USDC on Base via x402, with no signup or API key required.
      1
      MIT

    • agenti

      nirholas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP-compatible LLM client to autonomously hold, spend, earn, and receive cryptocurrency using native MCP tools, no code required.
      16 npm
      81
      ISC

    • pharos-paygate

      Oseodion
      A
      license
      B
      quality
      D
      maintenance
      Provides AI agents with a complete payments toolkit on the Pharos Atlantic Testnet, including balance checks, token transfers, conditional payments, batch sends, transaction history, gas estimation, and x402 protocol support.
      20
      3 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
    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.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap among sending variants (send_token, safe_transfer, conditional_payment, etc.), which could cause misselection if descriptions are not carefully read.

    Naming Consistency4/5

    All tools use snake_case with a verb_noun pattern, which is consistent. A few names like 'x402_pay_for_resource' break the pattern slightly, but overall it's predictable.

    Tool Count4/5

    20 tools is on the higher end but still reasonable for a comprehensive payment and DeFi server. Each tool serves a specific function, and the count is justified by the scope.

    Completeness5/5

    The tool set covers all major workflows: sending (multiple variants), receiving verification, wrapping/unwrapping, safety checks, balances, network stats, and pricing. No obvious gaps for the declared testnet domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources