A
licenseNot graded
qualityA
maintenanceEnables AI coding agents to add stablecoin checkout, create payment links and invoices, configure webhooks, verify payment signatures, and gate access based on confirmed payment events.
MIT
perly-pay-mcp
Related Servers
Alternatives to perly-pay-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.-
- FlicenseNot gradedqualityAmaintenanceLets AI coding agents integrate crypto checkout, payment links, payment status checks, and webhook-based entitlements into applications.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through crypto payment APIs.-
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to add stablecoin checkout, payment links, payment status checks, and webhook verification to applications, plus webhook-based access logic after confirmed payments.-
TDQS
B3.1/5.0
Scored across 38 tools
Disambiguation4/5
Most tools map to a distinct resource and action, and the descriptions clarify differences. However, create_invoice, create_checkout_session, create_payment_link, and create_subscription all represent ways to charge a buyer, so an agent may still need to reason carefully about which flow to use.
Naming Consistency5/5
Names consistently use snake_case with a verb-first pattern such as list_invoices, create_product, retrieve_receipt, and delete_webhook_endpoint. The one meta tool, pay_links, is slightly unusual semantically but still fits the snake_case convention.
Tool Count2/5
With 38 tools, the surface is well past the 25-tool threshold and feels heavy for an agent to navigate, even for a broad payments platform. Many resources have separate list/create/retrieve/update tools that could potentially be consolidated.
Completeness3/5
Core resources generally have create/list/retrieve coverage, and refunds, receipts, events, and webhooks are represented. But there are notable gaps: subscriptions lack update/cancel operations, customers lack update, and several resources such as products, prices, payment links, and refunds lack a retrieve operation.