LeashIndex Get the report

Index / payments

Pagar.me

io-github-mcp-dir-pagarme-mcp declares 86 capabilities across 86 tools, with 3 critical issues.

100/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://api.mcp.ai/p_pagarme, published in the official MCP registry as io.github.mcp-dir/pagarme-mcp 0.1.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 86 tools

86 of 86 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 16 of 86 tools

16 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 10 of 86 tools

10 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 86 tools

86 of 86 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 86 tools

86 of 86 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 25 of 86 tools

25 tools can modify data and declare no limit.

low · uncapped-read · 45 of 86 tools

45 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
pagarme_list_accountsread declared
pagarme_orders_listread declared
pagarme_orders_getread declared
pagarme_orders_get_manyread declared
pagarme_orders_write_createwrite inferred
pagarme_orders_write_updatewrite inferred
pagarme_orders_write_closedelete inferred
pagarme_charges_listread declared
pagarme_charges_summaryread declared
pagarme_charges_getread declared
pagarme_charges_get_manypay inferred
pagarme_charges_write_capturepay inferred
pagarme_charges_write_retrypay inferred
pagarme_charges_write_confirmpay inferred
pagarme_charges_write_update_due_datepay inferred
pagarme_charges_write_update_payment_methodpay inferred
pagarme_charges_write_update_cardpay inferred
pagarme_charges_cancelpay inferred
pagarme_customers_listread declared
pagarme_customers_getread declared
pagarme_customers_list_addressesread declared
pagarme_customers_get_addressread declared
pagarme_customers_write_createwrite inferred
pagarme_customers_write_updatewrite inferred
pagarme_customers_write_create_addresswrite inferred
pagarme_customers_write_update_addresswrite inferred
pagarme_customers_write_delete_addressdelete inferred
pagarme_cards_listread declared
pagarme_cards_getread declared
pagarme_cards_write_createwrite inferred
pagarme_cards_write_renewwrite inferred
pagarme_cards_deletedestructive declared
pagarme_plans_listread declared
pagarme_plans_getread declared
pagarme_plans_write_createwrite inferred
pagarme_plans_write_updatewrite inferred
pagarme_plans_deletedestructive declared
pagarme_subscriptions_listread declared
pagarme_subscriptions_getread declared
pagarme_subscriptions_itemsread declared
pagarme_subscriptions_cyclesread declared
pagarme_subscriptions_usagesread declared
pagarme_subscriptions_write_createwrite inferred
pagarme_subscriptions_write_update_cardwrite inferred
pagarme_subscriptions_write_update_payment_methodpay inferred
pagarme_subscriptions_write_update_billing_datewrite inferred
pagarme_subscriptions_write_add_itemwrite inferred
pagarme_subscriptions_write_add_usagewrite inferred
pagarme_subscriptions_canceldestructive declared
pagarme_recipients_listread declared
pagarme_recipients_getread declared
pagarme_recipients_defaultread declared
pagarme_recipients_balanceread declared
pagarme_recipients_transfersread declared
pagarme_recipients_withdrawalspay inferred
pagarme_recipients_anticipationsread declared
pagarme_recipients_anticipation_limitsread declared
pagarme_recipients_write_createwrite inferred
pagarme_recipients_write_updatewrite inferred
pagarme_recipients_write_update_bank_accountwrite inferred
pagarme_recipients_write_create_withdrawalwrite inferred
pagarme_recipients_write_create_anticipationwrite inferred
pagarme_transfers_listread declared
pagarme_transfers_getread declared
pagarme_transfers_writewrite inferred
pagarme_payables_listread declared
pagarme_payables_getread declared
pagarme_invoices_listread declared
pagarme_invoices_getread declared
pagarme_invoices_writewrite inferred
pagarme_invoices_canceldestructive declared
pagarme_legacy_list_transactionsread declared
pagarme_legacy_get_transactionread declared
pagarme_legacy_list_subscriptionsread declared
pagarme_legacy_list_plansread declared
pagarme_legacy_list_payablesread declared
pagarme_legacy_list_recipientsread declared
pagarme_legacy_list_customersread declared
pagarme_legacy_list_transfersread declared
pagarme_legacy_balanceread declared
show_versionread declared
report_bugwrite assumed
connectread declared
toolkit_inforead declared
marketplacewrite assumed
authenticatewrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.