mcpbeat

PagSeguro MCP Server

io.github.mcp-dir/pagseguro-mcp
answering

PagSeguro is answering right now. Last checked 6 min ago. It exposes 17 tools. Last commit 11 Jun 2026.

PagSeguro / PagBank payments, orders, charges (get, cancel, refund), checkouts and public key via th

Uptime history 40 hours of history · worst hour 50%
40 hours agonow
97.8%
Uptime 24h
89 of 91 checks
17
Tools
read from the server
575 ms
Response time
average over 24h
0
Stars
last commit 11 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add pagseguro-mcp --transport http https://api.mcp.ai/p_pagseguro
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "pagseguro-mcp": {
      "url": "https://api.mcp.ai/p_pagseguro"
    }
  }
}
~/.codex/config.toml
[mcp_servers.pagseguro-mcp]
url = "https://api.mcp.ai/p_pagseguro"
.cursor/mcp.json
{
  "mcpServers": {
    "pagseguro-mcp": {
      "url": "https://api.mcp.ai/p_pagseguro"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "pagseguro-mcp": {
      "url": "https://api.mcp.ai/p_pagseguro"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

pagseguro
pagseguro_charges_cancel
Cobranças (charges) no PagSeguro. Ações: - get: detalhe de UMA cobrança (requer charge_id). - cancel: cancela uma cobrança ainda não capturada (charge_id). - refund: estorna uma cobrança (charge_id; amount_cents opcional = estorno parcial). [Flattened action: cancel] Bulk support: accepts charge_ids for batched execution.
pagseguro_charges_get
Cobranças (charges) no PagSeguro. Ações: - get: detalhe de UMA cobrança (requer charge_id). - cancel: cancela uma cobrança ainda não capturada (charge_id). - refund: estorna uma cobrança (charge_id; amount_cents opcional = estorno parcial). [Flattened action: get] Bulk support: accepts charge_ids for batched execution.
pagseguro_charges_refund
Cobranças (charges) no PagSeguro. Ações: - get: detalhe de UMA cobrança (requer charge_id). - cancel: cancela uma cobrança ainda não capturada (charge_id). - refund: estorna uma cobrança (charge_id; amount_cents opcional = estorno parcial). [Flattened action: refund] Bulk support: accepts charge_ids for batched execution.
pagseguro_checkouts_create
Checkouts (links/sessões de pagamento) no PagSeguro. Ações: - create: cria um checkout (passe o objeto 'checkout'). - get: detalhe de UM checkout (requer checkout_id). - deactivate: inativa um checkout (checkout_id). [Flattened action: create] Bulk support: accepts checkout_ids for batched execution.
pagseguro_checkouts_deactivate
Checkouts (links/sessões de pagamento) no PagSeguro. Ações: - create: cria um checkout (passe o objeto 'checkout'). - get: detalhe de UM checkout (requer checkout_id). - deactivate: inativa um checkout (checkout_id). [Flattened action: deactivate] Bulk support: accepts checkout_ids for batched execution.
pagseguro_checkouts_get
Checkouts (links/sessões de pagamento) no PagSeguro. Ações: - create: cria um checkout (passe o objeto 'checkout'). - get: detalhe de UM checkout (requer checkout_id). - deactivate: inativa um checkout (checkout_id). [Flattened action: get] Bulk support: accepts checkout_ids for batched execution.
pagseguro_list_accounts
Lista tokens PagSeguro (contas de merchant) vinculados a este install — id e label.
pagseguro_orders_create
Pedidos (orders) no PagSeguro. Ações: - list: lista pedidos (⚠️ pode exigir reference_id; confirmar no probe). - get: detalhe de UM pedido (requer order_id). - create: cria um pedido (passe o objeto 'order' conforme a doc PagSeguro). [Flattened action: create] Bulk support: accepts order_ids, reference_ids for batched execution.
pagseguro_orders_get
Pedidos (orders) no PagSeguro. Ações: - list: lista pedidos (⚠️ pode exigir reference_id; confirmar no probe). - get: detalhe de UM pedido (requer order_id). - create: cria um pedido (passe o objeto 'order' conforme a doc PagSeguro). [Flattened action: get] Bulk support: accepts order_ids, reference_ids for batched execution.
pagseguro_orders_list
Pedidos (orders) no PagSeguro. Ações: - list: lista pedidos (⚠️ pode exigir reference_id; confirmar no probe). - get: detalhe de UM pedido (requer order_id). - create: cria um pedido (passe o objeto 'order' conforme a doc PagSeguro). [Flattened action: list] Bulk support: accepts order_ids, reference_ids for batched execution.
pagseguro_public_keys
Retorna a chave pública do merchant (para criptografar cartão no client). type default 'card'.
authenticate
authenticate
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.
connect
connect
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.
marketplace
marketplace
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.
report
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show
show_version
Show the current MCP platform and adapter versions.
toolkit
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes.

Endpoints

URLTransportStateLatencyChecked
https://api.mcp.ai/p_pagseguro streamable-http answering 564 ms 6 min ago

PagSeguro — questions

Answers built from our own checks of this server.

What can PagSeguro do?
It exposes 17 tools, read directly from the server on our last check. Among them: authenticate, connect, marketplace, pagseguro_charges_cancel, pagseguro_charges_get, pagseguro_charges_refund and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PagSeguro working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 575 ms. The bar chart above shows every period we have measured.
How do I connect PagSeguro?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PagSeguro need an API key?
No. PagSeguro completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PagSeguro?
It answers our handshake in 575 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is PagSeguro open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.