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.209 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.252 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.326 npmMIT
TDQS
B3.4/5.0
Scored across 29 tools
Disambiguation5/5
Each tool targets a distinct resource and action, from configuration and authentication to transactions, cashouts, customers, orders, products, and payment links. The generic api_request tool is clearly scoped as a fallback for routes without dedicated tools, preventing confusion.
Naming Consistency5/5
All tools follow a consistent safefy_payment_<verb>_<noun> pattern in snake_case, with only minor deviations like 'authenticate' and 'api_request'. This predictability makes it easy for an agent to infer function from the name.
Tool Count3/5
At 29 tools, the set is comprehensive but heavy. While most tools serve a clear purpose for a full payment API, the count edges into the 'too many' range and could be streamlined by consolidating niche operations like simulate and resend-webhook.
Completeness3/5
The set covers core operations for transactions, cashouts, customers, orders, products, and payment links, but lacks some lifecycle operations (e.g., refund/cancel transaction, update/delete product, create payment link). The generic api_request mitigates gaps but leaves the dedicated surface incomplete.
Maintenance
ActivityInactive
ResponsivenessNo issues