Pagar.me
REMOTE · API.MCP.AI · SCANNED SEP 27
Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (pagarme_charges_cancel) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 13674 tokens (~159/item across 86 items; 86 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 87 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Pagar.me MCP server?
Pagar.me is a hosted endpoint at https://api.mcp.ai/p_pagarme, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcp.ai
claude mcp add --transport http mcp-dir-pagarme-mcp 'https://api.mcp.ai/p_pagarme'
{
"mcpServers": {
"mcp-dir-pagarme-mcp": {
"url": "https://api.mcp.ai/p_pagarme"
}
}
} {
"servers": {
"mcp-dir-pagarme-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_pagarme"
}
}
} [mcp_servers.mcp-dir-pagarme-mcp] url = "https://api.mcp.ai/p_pagarme"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp-dir-pagarme-mcp": {
"type": "remote",
"url": "https://api.mcp.ai/p_pagarme",
"enabled": true
}
}
} openclaw mcp add mcp-dir-pagarme-mcp --url 'https://api.mcp.ai/p_pagarme' --transport streamable-http
mcp_servers:
mcp-dir-pagarme-mcp:
url: "https://api.mcp.ai/p_pagarme" {
"McpServers": {
"mcp-dir-pagarme-mcp": {
"Transport": "http",
"Url": "https://api.mcp.ai/p_pagarme"
}
}
} assistant mcp add mcp-dir-pagarme-mcp -t streamable-http -u 'https://api.mcp.ai/p_pagarme'
{
"mcpServers": {
"mcp-dir-pagarme-mcp": {
"type": "http",
"url": "https://api.mcp.ai/p_pagarme"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.346 → 0.9.351 functional
- 10 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.345 → 0.9.346 functional
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.343 → 0.9.345 functional
- 7 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.342 → 0.9.343 functional
- 6 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.340 → 0.9.342 functional
- 5 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.339 → 0.9.340 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://api.mcp.ai/p_pagarme
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 796a3b1f576e3f2e133c5d19d8f7be3b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mcp.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_pagarme | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_pagarme | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate ~99
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
marketplace ~532
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| arguments | string | – | – |
| cancel_comment | string | – | – |
| cancel_reason | string | – | – |
| conversation | string | – | – |
| immediate | boolean | – | – |
| limit | number | – | – |
| mcp_id | string | – | – |
| message | string | – | – |
| prompt_body | string | – | – |
| prompt_category | string | – | – |
| prompt_description | string | – | – |
| prompt_slug | string | – | – |
| prompt_targets | array | – | – |
| prompt_title | string | – | – |
| prompt_tool | string | – | – |
| prompt_vars | string | – | – |
| query | string | – | – |
| report_context | string | – | – |
| request_details | string | – | – |
| request_name | string | – | – |
| tier_slug | string | – | – |
| tool_id | string | – | – |
No output schema declared.
No examples provided.
pagarme_cards_delete ~89
Remove um cartão salvo do cliente no Pagar.me V5 (requer customer_id + card_id). Irreversível. Bulk support: accepts customer_ids, card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| card_id | string | yes | – |
| card_ids | array | – | – |
| customer_id | string | yes | – |
| customer_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_cards_get ~107
Cartões salvos de um cliente no Pagar.me V5. Ações (requerem customer_id): - list: lista cartões. - get: cartão por card_id. [Flattened action: get] Bulk support: accepts customer_ids, card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| card_id | string | – | – |
| card_ids | array | – | – |
| customer_id | string | yes | – |
| customer_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_cards_list ~107
Cartões salvos de um cliente no Pagar.me V5. Ações (requerem customer_id): - list: lista cartões. - get: cartão por card_id. [Flattened action: list] Bulk support: accepts customer_ids, card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| card_id | string | – | – |
| card_ids | array | – | – |
| customer_id | string | yes | – |
| customer_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_cards_write_create ~146
Criar/renovar cartões de um cliente no Pagar.me V5 (só sk_; requer customer_id). Ações: - create: tokeniza/salva cartão (data: number, holder_name, exp_month, exp_year, cvv ou card_token). - renew: renova cartão (requer card_id). [Flattened action: create] Bulk support: accepts customer_ids, card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| card_id | string | – | – |
| card_ids | array | – | – |
| customer_id | string | yes | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_cards_write_renew ~147
Criar/renovar cartões de um cliente no Pagar.me V5 (só sk_; requer customer_id). Ações: - create: tokeniza/salva cartão (data: number, holder_name, exp_month, exp_year, cvv ou card_token). - renew: renova cartão (requer card_id). [Flattened action: renew] Bulk support: accepts customer_ids, card_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| card_id | string | – | – |
| card_ids | array | – | – |
| customer_id | string | yes | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_cancel ~87
Cancela/estorna uma cobrança no Pagar.me V5 (requer charge_id; data opcional com amount p/ estorno parcial). Irreversível. Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_get ~147
Cobranças (charges) no Pagar.me V5. Ações: - list: lista paginada (page, size; filtros via data: status, payment_method, customer_id, order_id, created_since/until). - summary: agregado de cobranças (data: status, created_since/until). - get: detalhe por charge_id. - get_many: vários por charge_ids (lote). [Flattened action: get]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | – | – |
| charge_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_charges_get_many ~149
Cobranças (charges) no Pagar.me V5. Ações: - list: lista paginada (page, size; filtros via data: status, payment_method, customer_id, order_id, created_since/until). - summary: agregado de cobranças (data: status, created_since/until). - get: detalhe por charge_id. - get_many: vários por charge_ids (lote). [Flattened action: get_many]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | – | – |
| charge_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_charges_list ~147
Cobranças (charges) no Pagar.me V5. Ações: - list: lista paginada (page, size; filtros via data: status, payment_method, customer_id, order_id, created_since/until). - summary: agregado de cobranças (data: status, created_since/until). - get: detalhe por charge_id. - get_many: vários por charge_ids (lote). [Flattened action: list]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | – | – |
| charge_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_charges_summary ~147
Cobranças (charges) no Pagar.me V5. Ações: - list: lista paginada (page, size; filtros via data: status, payment_method, customer_id, order_id, created_since/until). - summary: agregado de cobranças (data: status, created_since/until). - get: detalhe por charge_id. - get_many: vários por charge_ids (lote). [Flattened action: summary]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | – | – |
| charge_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_capture ~160
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: capture] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_confirm ~160
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: confirm] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_retry ~160
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: retry] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_update_card ~162
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: update_card] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_update_due_date ~164
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: update_due_date] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_charges_write_update_payment_method ~164
Operar cobranças no Pagar.me V5 (só contas sk_; não-destrutivas). Ações (requerem charge_id): - capture: captura (data opcional: amount). - retry: reprocessa. - confirm: confirma pagamento (cash/voucher; data opcional). - update_due_date: altera vencimento (data: { due_at }). - update_payment_method: altera meio de pagamento (data). - update_card: altera cartão (data). [Flattened action: update_payment_method] Bulk support: accepts charge_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| charge_id | string | yes | – |
| charge_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_customers_get ~164
Clientes e endereços no Pagar.me V5. Ações: - list: lista clientes (page, size; data: name, email, document, code). - get: cliente por customer_id. - list_addresses: endereços do cliente (requer customer_id). - get_address: endereço (requer customer_id + address_id). [Flattened action: get] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_customers_get_address ~166
Clientes e endereços no Pagar.me V5. Ações: - list: lista clientes (page, size; data: name, email, document, code). - get: cliente por customer_id. - list_addresses: endereços do cliente (requer customer_id). - get_address: endereço (requer customer_id + address_id). [Flattened action: get_address] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_customers_list ~164
Clientes e endereços no Pagar.me V5. Ações: - list: lista clientes (page, size; data: name, email, document, code). - get: cliente por customer_id. - list_addresses: endereços do cliente (requer customer_id). - get_address: endereço (requer customer_id + address_id). [Flattened action: list] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_customers_list_addresses ~166
Clientes e endereços no Pagar.me V5. Ações: - list: lista clientes (page, size; data: name, email, document, code). - get: cliente por customer_id. - list_addresses: endereços do cliente (requer customer_id). - get_address: endereço (requer customer_id + address_id). [Flattened action: list_addresses] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_customers_write_create ~184
Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações: - create: cria cliente (data: name, email, document, type, …). - update: atualiza cliente (requer customer_id; data). - create_address: cria endereço (requer customer_id; data). - update_address: atualiza endereço (requer customer_id + address_id; data). - delete_address: remove endereço (requer customer_id + address_id). [Flattened action: create] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_customers_write_create_address ~186
Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações: - create: cria cliente (data: name, email, document, type, …). - update: atualiza cliente (requer customer_id; data). - create_address: cria endereço (requer customer_id; data). - update_address: atualiza endereço (requer customer_id + address_id; data). - delete_address: remove endereço (requer customer_id + address_id). [Flattened action: create_address] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_customers_write_delete_address ~186
Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações: - create: cria cliente (data: name, email, document, type, …). - update: atualiza cliente (requer customer_id; data). - create_address: cria endereço (requer customer_id; data). - update_address: atualiza endereço (requer customer_id + address_id; data). - delete_address: remove endereço (requer customer_id + address_id). [Flattened action: delete_address] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_customers_write_update ~184
Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações: - create: cria cliente (data: name, email, document, type, …). - update: atualiza cliente (requer customer_id; data). - create_address: cria endereço (requer customer_id; data). - update_address: atualiza endereço (requer customer_id + address_id; data). - delete_address: remove endereço (requer customer_id + address_id). [Flattened action: update] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_customers_write_update_address ~186
Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações: - create: cria cliente (data: name, email, document, type, …). - update: atualiza cliente (requer customer_id; data). - create_address: cria endereço (requer customer_id; data). - update_address: atualiza endereço (requer customer_id + address_id; data). - delete_address: remove endereço (requer customer_id + address_id). [Flattened action: update_address] Bulk support: accepts customer_ids, address_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| address_id | string | – | – |
| address_ids | array | – | – |
| customer_id | string | – | – |
| customer_ids | array | – | – |
| data | string | – | – |
No output schema declared.
No examples provided.
pagarme_invoices_cancel ~67
Cancela uma fatura no Pagar.me V5 (requer invoice_id). Irreversível. Bulk support: accepts invoice_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| invoice_id | string | yes | – |
| invoice_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_invoices_get ~126
Faturas (invoices) de assinatura no Pagar.me V5. Ações: - list: lista faturas (page, size; data: subscription_id, customer_id, status, due_since/until). - get: fatura por invoice_id. [Flattened action: get] Bulk support: accepts invoice_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| invoice_id | string | – | – |
| invoice_ids | array | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_invoices_list ~126
Faturas (invoices) de assinatura no Pagar.me V5. Ações: - list: lista faturas (page, size; data: subscription_id, customer_id, status, due_since/until). - get: fatura por invoice_id. [Flattened action: list] Bulk support: accepts invoice_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| invoice_id | string | – | – |
| invoice_ids | array | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_invoices_write ~84
Altera o status de uma fatura no Pagar.me V5 (requer invoice_id + status, ex.: 'paid', 'canceled'). Bulk support: accepts invoice_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| invoice_id | string | yes | – |
| invoice_ids | array | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
pagarme_legacy_balance ~201
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: balance] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_get_transaction ~203
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: get_transaction] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_customers ~205
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_customers] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_payables ~205
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_payables] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_plans ~205
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_plans] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_recipients ~207
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_recipients] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_subscriptions ~205
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_subscriptions] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_transactions ~203
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_transactions] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_legacy_list_transfers ~205
Leitura da API LEGADA V1–V4 do Pagar.me (modelo "transactions"). Ativa quando a conexão usa uma chave ak_… (contas ainda não migradas pra V5). As 4 versões legadas compartilham estes endpoints; diferenças de campo entre V1/V2/V3/V4 vêm cruas no payload. Ações: - list_transactions / get_transaction (requer transaction_id) - list_subscriptions / list_plans / list_payables / list_recipients / list_customers / list_transfers - balance: saldo da conta Filtros de lista (count, page, status, …) via data (JSON). [Flattened action: list_transfers] Bulk support: accepts transaction_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| transaction_id | string | – | – |
| transaction_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_list_accounts ~49
Lista as contas Pagar.me (chaves) conectadas a este install — id, label e versão (V5 ou legado V1–V4).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
pagarme_orders_get ~129
Pedidos (orders) no Pagar.me V5. Ações: - list: lista paginada (page, size, code, status, customer_id, created_since, created_until). - get: detalhe por order_id. - get_many: busca vários por order_ids (lote, retorna { results, errors }). [Flattened action: get]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_orders_get_many ~131
Pedidos (orders) no Pagar.me V5. Ações: - list: lista paginada (page, size, code, status, customer_id, created_since, created_until). - get: detalhe por order_id. - get_many: busca vários por order_ids (lote, retorna { results, errors }). [Flattened action: get_many]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_orders_list ~129
Pedidos (orders) no Pagar.me V5. Ações: - list: lista paginada (page, size, code, status, customer_id, created_since, created_until). - get: detalhe por order_id. - get_many: busca vários por order_ids (lote, retorna { results, errors }). [Flattened action: list]
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
| page | number | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_orders_write_close ~154
Criar/atualizar/fechar pedidos no Pagar.me V5 (só contas sk_). Ações: - create: cria pedido. data = JSON do pedido (customer/customer_id, items[], payments[]). - update: atualiza pedido (requer order_id). data = campos a alterar. - close: fecha (closed:true) ou reabre (closed:false) o pedido (requer order_id). [Flattened action: close] Bulk support: accepts order_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| closed | boolean | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_orders_write_create ~154
Criar/atualizar/fechar pedidos no Pagar.me V5 (só contas sk_). Ações: - create: cria pedido. data = JSON do pedido (customer/customer_id, items[], payments[]). - update: atualiza pedido (requer order_id). data = campos a alterar. - close: fecha (closed:true) ou reabre (closed:false) o pedido (requer order_id). [Flattened action: create] Bulk support: accepts order_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| closed | boolean | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_orders_write_update ~154
Criar/atualizar/fechar pedidos no Pagar.me V5 (só contas sk_). Ações: - create: cria pedido. data = JSON do pedido (customer/customer_id, items[], payments[]). - update: atualiza pedido (requer order_id). data = campos a alterar. - close: fecha (closed:true) ou reabre (closed:false) o pedido (requer order_id). [Flattened action: update] Bulk support: accepts order_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| closed | boolean | – | – |
| data | string | – | – |
| order_id | string | – | – |
| order_ids | array | – | – |
No output schema declared.
No examples provided.
pagarme_payables_get ~121
Recebíveis (payables) no Pagar.me V5. Ações: - list: lista recebíveis (page, size; data: status, payment_date, type, …). - get: recebível por payable_id. [Flattened action: get] Bulk support: accepts payable_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| page | number | – | – |
| payable_id | string | – | – |
| payable_ids | array | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
pagarme_payables_list ~121
Recebíveis (payables) no Pagar.me V5. Ações: - list: lista recebíveis (page, size; data: status, payment_date, type, …). - get: recebível por payable_id. [Flattened action: list] Bulk support: accepts payable_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| data | string | – | – |
| page | number | – | – |
| payable_id | string | – | – |
| payable_ids | array | – | – |
| size | number | – | – |
No output schema declared.
No examples provided.
What is the Pagar.me MCP server?
Pagar.me is an MCP server listed in the public MCP registry as io.github.mcp-dir/pagarme-mcp. Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p. This page covers its hosted endpoint (https://api.mcp.ai/p_pagarme).
Is the Pagar.me MCP server safe to use?
Pagar.me scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pagar.me MCP server expose?
Pagar.me exposes 86 tools: pagarme_list_accounts, pagarme_orders_list, pagarme_orders_get, pagarme_orders_get_many, pagarme_orders_write_create, and 81 more. Their descriptions and schemas cost roughly 13,549 tokens of context every time the server is loaded.
Does the Pagar.me MCP server require authentication?
No. We connected to Pagar.me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pagar.me MCP server still maintained?
Pagar.me is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.