Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pagar.me

REMOTE · API.MCP.AI

Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p

Available components

0 this week 68 Trust /100

Last scanned (14 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.460 → 0.9.467 functional
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.459 → 0.9.460 functional
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.454 → 0.9.459 functional
  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.452 → 0.9.454 functional
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.450 → 0.9.452 functional
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.449 → 0.9.450 functional
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.442 → 0.9.449 functional
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.429 → 0.9.442 functional
Diagnostics

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 21 Nov 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 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1bf4d405299e078a0e62ff16cded599b
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. DS published 1814 8 Verified
mcp.ai. No DS 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
MCP tools · 86 exposed · ~13,549 tokens

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 →

Tool Tokens
pagarme_plans_delete ~65

Remove um plano no Pagar.me V5 (requer plan_id). Irreversível. Bulk support: accepts plan_ids for batched execution.

NameTypeReqDescription
accountstring––
plan_idstringyes–
plan_idsarray––

No output schema declared.

No examples provided.

pagarme_plans_get ~111

Planos de assinatura no Pagar.me V5. Ações: - list: lista planos (page, size; data: name, status). - get: plano por plan_id. [Flattened action: get] Bulk support: accepts plan_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
plan_idstring––
plan_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_plans_list ~111

Planos de assinatura no Pagar.me V5. Ações: - list: lista planos (page, size; data: name, status). - get: plano por plan_id. [Flattened action: list] Bulk support: accepts plan_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
plan_idstring––
plan_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_plans_write_create ~115

Criar/atualizar planos no Pagar.me V5 (só sk_). Ações: - create: cria plano (data: name, interval, interval_count, items[], …). - update: atualiza plano (requer plan_id; data). [Flattened action: create] Bulk support: accepts plan_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
plan_idstring––
plan_idsarray––

No output schema declared.

No examples provided.

pagarme_plans_write_update ~115

Criar/atualizar planos no Pagar.me V5 (só sk_). Ações: - create: cria plano (data: name, interval, interval_count, items[], …). - update: atualiza plano (requer plan_id; data). [Flattened action: update] Bulk support: accepts plan_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
plan_idstring––
plan_idsarray––

No output schema declared.

No examples provided.

pagarme_recipients_anticipation_limits ~205

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: anticipation_limits] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_anticipations ~204

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: anticipations] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_balance ~201

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: balance] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_default ~201

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: default] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_get ~201

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: get] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_list ~201

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: list] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_transfers ~202

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: transfers] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_withdrawals ~203

Recebedores (split/marketplace) no Pagar.me V5. Ações: - list: lista recebedores (page, size). - get: recebedor por recipient_id. - default: recebedor padrão (a própria conta). - balance: saldo do recebedor (requer recipient_id). - transfers: transferências do recebedor (requer recipient_id). - withdrawals: saques do recebedor (requer recipient_id). - anticipations: antecipações do recebedor (requer recipient_id). - anticipation_limits: limites de antecipação (requer recipient_id). [Flattened action: withdrawals] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
recipient_idstring––
recipient_idsarray––
sizenumber––

No output schema declared.

No examples provided.

pagarme_recipients_write_create ~165

Criar/operar recebedores no Pagar.me V5 (só sk_). Ações: - create: cria recebedor (data). - update: atualiza recebedor (requer recipient_id; data). - update_bank_account: atualiza conta bancária (requer recipient_id; data). - create_withdrawal: cria saque (requer recipient_id; data: { amount }). - create_anticipation: cria antecipação (requer recipient_id; data). [Flattened action: create] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
recipient_idstring––
recipient_idsarray––

No output schema declared.

No examples provided.

pagarme_recipients_write_create_anticipation ~171

Criar/operar recebedores no Pagar.me V5 (só sk_). Ações: - create: cria recebedor (data). - update: atualiza recebedor (requer recipient_id; data). - update_bank_account: atualiza conta bancária (requer recipient_id; data). - create_withdrawal: cria saque (requer recipient_id; data: { amount }). - create_anticipation: cria antecipação (requer recipient_id; data). [Flattened action: create_anticipation] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
recipient_idstring––
recipient_idsarray––

No output schema declared.

No examples provided.

pagarme_recipients_write_create_withdrawal ~171

Criar/operar recebedores no Pagar.me V5 (só sk_). Ações: - create: cria recebedor (data). - update: atualiza recebedor (requer recipient_id; data). - update_bank_account: atualiza conta bancária (requer recipient_id; data). - create_withdrawal: cria saque (requer recipient_id; data: { amount }). - create_anticipation: cria antecipação (requer recipient_id; data). [Flattened action: create_withdrawal] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
recipient_idstring––
recipient_idsarray––

No output schema declared.

No examples provided.

pagarme_recipients_write_update ~165

Criar/operar recebedores no Pagar.me V5 (só sk_). Ações: - create: cria recebedor (data). - update: atualiza recebedor (requer recipient_id; data). - update_bank_account: atualiza conta bancária (requer recipient_id; data). - create_withdrawal: cria saque (requer recipient_id; data: { amount }). - create_anticipation: cria antecipação (requer recipient_id; data). [Flattened action: update] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
recipient_idstring––
recipient_idsarray––

No output schema declared.

No examples provided.

pagarme_recipients_write_update_bank_account ~169

Criar/operar recebedores no Pagar.me V5 (só sk_). Ações: - create: cria recebedor (data). - update: atualiza recebedor (requer recipient_id; data). - update_bank_account: atualiza conta bancária (requer recipient_id; data). - create_withdrawal: cria saque (requer recipient_id; data: { amount }). - create_anticipation: cria antecipação (requer recipient_id; data). [Flattened action: update_bank_account] Bulk support: accepts recipient_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
recipient_idstring––
recipient_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_cancel ~83

Cancela uma assinatura no Pagar.me V5 (requer subscription_id; data opcional: { cancel_pending_invoices }). Irreversível. Bulk support: accepts subscription_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
subscription_idstringyes–
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_cycles ~181

Assinaturas no Pagar.me V5. Ações: - list: lista assinaturas (page, size; data: customer_id, plan_id, status, created_since/until). - get: assinatura por subscription_id. - items: itens da assinatura (requer subscription_id). - cycles: ciclos da assinatura (requer subscription_id). - usages: usos de um item medido (requer subscription_id + item_id). [Flattened action: cycles] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
pagenumber––
sizenumber––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_get ~181

Assinaturas no Pagar.me V5. Ações: - list: lista assinaturas (page, size; data: customer_id, plan_id, status, created_since/until). - get: assinatura por subscription_id. - items: itens da assinatura (requer subscription_id). - cycles: ciclos da assinatura (requer subscription_id). - usages: usos de um item medido (requer subscription_id + item_id). [Flattened action: get] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
pagenumber––
sizenumber––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_items ~181

Assinaturas no Pagar.me V5. Ações: - list: lista assinaturas (page, size; data: customer_id, plan_id, status, created_since/until). - get: assinatura por subscription_id. - items: itens da assinatura (requer subscription_id). - cycles: ciclos da assinatura (requer subscription_id). - usages: usos de um item medido (requer subscription_id + item_id). [Flattened action: items] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
pagenumber––
sizenumber––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_list ~181

Assinaturas no Pagar.me V5. Ações: - list: lista assinaturas (page, size; data: customer_id, plan_id, status, created_since/until). - get: assinatura por subscription_id. - items: itens da assinatura (requer subscription_id). - cycles: ciclos da assinatura (requer subscription_id). - usages: usos de um item medido (requer subscription_id + item_id). [Flattened action: list] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
pagenumber––
sizenumber––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_usages ~182

Assinaturas no Pagar.me V5. Ações: - list: lista assinaturas (page, size; data: customer_id, plan_id, status, created_since/until). - get: assinatura por subscription_id. - items: itens da assinatura (requer subscription_id). - cycles: ciclos da assinatura (requer subscription_id). - usages: usos de um item medido (requer subscription_id + item_id). [Flattened action: usages] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
pagenumber––
sizenumber––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_add_item ~220

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: add_item] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_add_usage ~220

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: add_usage] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_create ~218

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: create] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_update_billing_date ~224

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: update_billing_date] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_update_card ~220

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: update_card] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_subscriptions_write_update_payment_method ~222

Criar/operar assinaturas no Pagar.me V5 (só sk_; não-destrutivas). Ações: - create: cria assinatura (data: customer_id/customer, plan_id ou items[], payment_method, card_id, …). - update_card: altera cartão (requer subscription_id; data). - update_payment_method: altera meio de pagamento (requer subscription_id; data). - update_billing_date: altera data de cobrança (requer subscription_id; data). - add_item: adiciona item (requer subscription_id; data). - add_usage: registra uso de item medido (requer subscription_id + item_id; data opcional). [Flattened action: update_payment_method] Bulk support: accepts subscription_ids, item_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
item_idstring––
item_idsarray––
subscription_idstring––
subscription_idsarray––

No output schema declared.

No examples provided.

pagarme_transfers_get ~108

Transferências no Pagar.me V5. Ações: - list: lista transferências (page, size; data: filtros). - get: transferência por transfer_id. [Flattened action: get] Bulk support: accepts transfer_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
sizenumber––
transfer_idstring––
transfer_idsarray––

No output schema declared.

No examples provided.

pagarme_transfers_list ~108

Transferências no Pagar.me V5. Ações: - list: lista transferências (page, size; data: filtros). - get: transferência por transfer_id. [Flattened action: list] Bulk support: accepts transfer_ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
pagenumber––
sizenumber––
transfer_idstring––
transfer_idsarray––

No output schema declared.

No examples provided.

pagarme_transfers_write ~54

Cria uma transferência no Pagar.me V5 (só sk_). data = JSON do corpo (amount, recipient_id, …).

NameTypeReqDescription
accountstring––
datastringyes–

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http mcp-dir-pagarme-mcp 'https://api.mcp.ai/p_pagarme'
Common questions

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 68 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Pagar.me MCP server?

VerifyMCP ran 11 checks on Pagar.me, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Pagar.me: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.