paygentic
Related Servers
Alternatives to paygentic
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables financial management through the Procfy API, allowing AI agents to manage transactions, bank accounts, contacts, and more via natural language.1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.3 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to manage personal expenses through natural language conversations. Supports adding, searching, and analyzing transactions with automatic categorization and financial insights.3MIT

PayAgents MCP Serverofficial
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.314 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.73 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to hold wallets, make payments, and charge for services using the Setu payment network.2 npmMIT
TDQS
Scored across 13 tools
Each tool has a well-defined and distinct purpose, covering wallet management, invoices, policies, transactions, and account setup. Even similar actions like sending money and requesting payment are clearly differentiated by their descriptions.
All tools follow a consistent `verb_noun` pattern with the `paygentic_` prefix. The verbs are clear and the nouns are specific, making the tool names predictable and easy to interpret.
With 13 tools, the server covers a comprehensive set of operations for a payment/wallet system without being overwhelming. The count is well within the typical 3-15 range for a focused service.
The server covers core operations like creating wallets, handling invoices, setting policies, and sending money. Minor gaps exist, such as missing update/delete for wallets and invoices, but these are not critical for basic functionality.