mcp-registry/io.github.mcp-dir/pagarme-mcp · v0.9.372
Also listed as glama/mcp-dir/pagar.me
As of 2026-10-18 15:34 UTC, the Mcp Dir Pagarme MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.
Stone's payments gateway (api.pagar.me), orders, charges (card, Pix, boleto), customers and cards, p
Claude Code
claude mcp add --transport http mcp-dir-pagarme-mcp-server https://api.mcp.ai/p_pagarme
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mcp-dir-pagarme-mcp-server": {
"type": "http",
"url": "https://api.mcp.ai/p_pagarme"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
86 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
454 parameter(s) across 83 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Loading this server's tool list costs an agent ~17,504 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Reachable 99.0% of the time over the last 30 days; median recovery 6 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
23 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mcp-dir/pagarme-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mcp-dir/pagarme-mcp"}) over MCP.
marketplace ~570 tokenspagarme_subscriptions_write_update_payment_method ~255 tokenspagarme_subscriptions_write_update_billing_date ~254 tokenspagarme_customers_write_create_address ~252 tokenspagarme_customers_write_delete_address ~252 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fpagarme-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fpagarme-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcp-dir%2Fpagarme-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mcp-dir%2Fpagarme-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mcp-dir%2Fpagarme-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5cd27936078ccb23…, first seen 2026-10-17, included at leaf 1273 of 22,675. Version history · verify what your client received.
Compare: most reliable authentication servers · most reliable other servers · most reliable marketplace servers · most reliable finance servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 15:34 UTC, the Mcp Dir Pagarme MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 24 outages in 90 days, with a median recovery of 6 minutes.
Mcp Dir Pagarme MCP server advertises 86 tools, including authenticate, connect, marketplace, pagarme_cards_delete, pagarme_cards_get.
Point your MCP client at this streamable-http endpoint: https://api.mcp.ai/p_pagarme
Glimind scanned all 86 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.