A
licenseNot graded
qualityD
maintenanceMCP server that enables AI agents to manage PagSeguro/PagBank payments, including orders, charges, checkouts, and public keys via official API.
MIT
Safefy MCP
Officialby Safefy-Pay
Related Servers
Alternatives to Safefy MCP
No user-submitted related servers found.
Related Servers
zuckpay-mcpofficial
AlicenseAqualityAmaintenanceOfficial MCP server for ZuckPay – create PIX, SPEI, and PayPal charges, and query transactions from your AI assistant.2012 npmMIT
OrcaRail MCPofficial
AlicenseBqualityAmaintenanceOfficial MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.26189 npmMIT- AlicenseNot gradedqualityFmaintenanceMCP server for Stone's payment gateway, enabling AI agents to manage orders, charges, customers, subscriptions, and more via the Pagar.me API.MIT
- AlicenseAqualityCmaintenanceMCP server for DePix App that enables AI agents to receive Pix payments and read transaction status via the DePix API.161,337 npmApache 2.0
- AlicenseBqualityCmaintenanceOfficial MCP server for ZapifyAPI, providing AI agents access to 32 tools across image conversion, text analysis, network diagnostics, developer utilities, and data conversion.3223 npmMIT
TDQS
B3.3/5.0
Scored across 29 tools
Disambiguation4/5
Most tools map to a distinct resource+action (transactions, cashouts, orders, customers, products, payment links), so selection is generally clear. Minor ambiguity exists among the meta/config tools (list_capabilities, get_configuration, authenticate, configure_credentials, get_integration_guide) and the generic api_request fallback, which overlaps with every dedicated tool by design.
Naming Consistency5/5
Every tool follows the same safefy_payment_<verb>_<noun> snake_case convention (list_, get_, create_, update_, cancel_, simulate_, resend_, start_). The pattern is highly predictable and consistent throughout all 29 tools.
Tool Count3/5
At 29 tools the set is heavy, especially with six non-CRUD meta/config tools (capabilities, configuration, authenticate, credentials, integration guide, api_request) that pad the surface. The breadth of domain (payments, cashouts, orders, customers, products, links) partly justifies the count, but it sits in borderline territory.
Completeness4/5
Coverage is broad with create/list/get/update for customers and create/list/get for orders, plus full cashout lifecycle. Gaps remain: no product create/update/delete, no transaction refund/cancel, and no order mutation, though the generic api_request fallback lets agents reach uncovered routes.
Maintenance
ActivityMaintained
ResponsivenessNo issues