pharos-paygate
Related Servers
Alternatives to pharos-paygate
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI agents to autonomously make policy-controlled payments for APIs and tools via Bitcoin Lightning (L402) and Base USDC (x402), including paying paywalled endpoints, checking balances, and reviewing transactions.37 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to make gasless payments on Pharos blockchain using x402/EIP-3009, with automatic on-chain reputation tracking and a leaderboard.1-
- AlicenseAqualityDmaintenanceEnables AI agents to call x402-gated APIs using a central credit balance, abstracting away blockchain complexity and payment proofs. It provides tools to fetch data from payment-required endpoints, check usage balances, and simulate transaction costs.640 npm2-

@coinbase/payments-mcpofficial
AlicenseNot gradedqualityFmaintenanceCombines wallets, onramps, and payments via x402 to enable AI agents to autonomously discover and pay for services without API keys or complex setup.42 npm58Apache 2.0- AlicenseNot gradedqualityCmaintenanceProvides Tezos wallet management and blockchain interaction tools for AI agents, including support for the x402 payment protocol. It enables tasks like sending XTZ, checking balances, and managing automated payments for services like NFT minting.4Apache 2.0
- AlicenseAqualityDmaintenanceA drop-in MCP skill that gives AI agents a real on-chain wallet on Pharos — check balances, read live prices, move tokens, pay only when conditions are met, screen for scams, and buy x402 pay-per-use APIs, all from natural language.206 npmMIT
TDQS
Scored across 20 tools
Several tools have overlapping purposes, especially around sending tokens: send_usdc is redundant with send_token (which also sends USDC), and conditional_payment, batch_send, safe_transfer, and multi_condition_payment all perform send-like operations with different modifiers. While descriptions help differentiate them, an agent may still struggle to select the correct one.
Most tool names follow a consistent verb_noun pattern in snake_case (e.g., get_wallet_balances, check_token_safety). However, a few names like safe_transfer (verb missing), conditional_payment (noun first), and x402_pay_for_resource (unusual prefix) deviate slightly from the pattern.
With 20 tools, the server covers a broad range of payment-related operations. While this is on the higher end of the ideal range, each tool serves a distinct purpose in the domain of wallet management, token transfers, safety checks, and network queries. The count feels slightly heavy but not excessive.
The tool set covers most essential operations: balance checks, price queries, token sending (with variants), safety screening, gas estimation, payment requests, transaction history, and wrapping. Minor gaps exist, such as the lack of a tool to list supported tokens or cancel payment requests, but agents can typically work around these.