Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/mcp-dir, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸pagarme_list_accounts68C
▸pagarme_orders_list68C
▸pagarme_orders_get68C
▸pagarme_orders_get_many68C
▸pagarme_orders_write_create68C
▸pagarme_orders_write_update68C
▸pagarme_orders_write_close68C
▸pagarme_charges_list68C
▸pagarme_charges_summary68C
▸pagarme_charges_get68C
▸pagarme_charges_get_many68C
▸pagarme_charges_write_capture75B
▸pagarme_charges_write_retry75B
▸pagarme_charges_write_confirm75B
▸pagarme_charges_write_update_due_date75B
▸pagarme_charges_write_update_payment_method75B
▸pagarme_charges_write_update_card75B
▸pagarme_charges_cancel75B
▸pagarme_customers_list68C
▸pagarme_customers_get68C
▸pagarme_customers_list_addresses68C
▸pagarme_customers_get_address68C
▸pagarme_customers_write_create68C
▸pagarme_customers_write_update68C
▸pagarme_customers_write_create_address68C
▸pagarme_customers_write_update_address68C
▸pagarme_customers_write_delete_address68C
▸pagarme_cards_list75B
▸pagarme_cards_get75B
▸pagarme_cards_write_create75B
▸pagarme_cards_write_renew75B
▸pagarme_cards_delete75B
▸pagarme_plans_list68C
▸pagarme_plans_get68C
▸pagarme_plans_write_create68C
▸pagarme_plans_write_update68C
▸pagarme_plans_delete75B
▸pagarme_subscriptions_list68C
▸pagarme_subscriptions_get68C
▸pagarme_subscriptions_items68C
▸pagarme_subscriptions_cycles68C
▸pagarme_subscriptions_usages68C
▸pagarme_subscriptions_write_create68C
▸pagarme_subscriptions_write_update_card68C
▸pagarme_subscriptions_write_update_payment_method68C
▸pagarme_subscriptions_write_update_billing_date68C
▸pagarme_subscriptions_write_add_item68C
▸pagarme_subscriptions_write_add_usage68C
▸pagarme_subscriptions_cancel75B
▸pagarme_recipients_list68C
▸pagarme_recipients_get68C
▸pagarme_recipients_default68C
▸pagarme_recipients_balance68C
▸pagarme_recipients_transfers68C
▸pagarme_recipients_withdrawals68C
▸pagarme_recipients_anticipations68C
▸pagarme_recipients_anticipation_limits68C
▸pagarme_recipients_write_create68C
▸pagarme_recipients_write_update68C
▸pagarme_recipients_write_update_bank_account68C
▸pagarme_recipients_write_create_withdrawal68C
▸pagarme_recipients_write_create_anticipation68C
▸pagarme_transfers_list68C
▸pagarme_transfers_get68C
▸pagarme_transfers_write75B
▸pagarme_payables_list68C
▸pagarme_payables_get68C
▸pagarme_invoices_list68C
▸pagarme_invoices_get68C
▸pagarme_invoices_write75B
▸pagarme_invoices_cancel75B
▸pagarme_legacy_list_transactions68C
▸pagarme_legacy_get_transaction68C
▸pagarme_legacy_list_subscriptions68C
▸pagarme_legacy_list_plans68C
▸pagarme_legacy_list_payables68C
▸pagarme_legacy_list_recipients68C
▸pagarme_legacy_list_customers68C
▸pagarme_legacy_list_transfers68C
▸pagarme_legacy_balance68C
▸show_version75B
▸report_bug75B
▸connect100A
▸toolkit_info100A
▸marketplace68C
▸authenticate68C
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +18 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
Push to the repo or cut a release. Activity within the last 30 days earns the full 45.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
- 1 of 1 params have no description: `account`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 6 of 6 params have no description: `data`, `page`, `size`, `account`, +2 more. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 6 of 6 params have no description: `data`, `page`, `size`, `account`, +2 more. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 6 of 6 params have no description: `data`, `page`, `size`, `account`, +2 more. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
Already earned (4) ▾Already earned (4) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.mcp-dir/pagarme-mcp)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"pagarme": {
"command": "npx",
"args": [
"-y",
"pagarme-mcp"
]
}
}
}▶ Try itlive against api.mcp.ai
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.