Should my agent depend on the MCP server io.github.mcp-dir/pagarme-mcp?

Verdict: allow — gateway — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Pagar.me

io.github.mcp-dir/pagarme-mcp

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

— the operator's own registry description reported

Publisher io.github.mcp-dir · first seen 2026-08-12 · endpoint https://api.mcp.ai/p_pagarme

allow

verdict

gateway

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — gateway — safe to depend on

Cluster gateway · distinctiveness 0.605 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency724 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools86

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identityfarm_member

servers on its host99

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_4aed1908300f988bc9bd9ff9 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

authenticate connect marketplace pagarme_cards_delete pagarme_cards_get pagarme_cards_list pagarme_cards_write_create pagarme_cards_write_renew pagarme_charges_cancel pagarme_charges_get pagarme_charges_get_many pagarme_charges_list pagarme_charges_summary pagarme_charges_write_capture pagarme_charges_write_confirm pagarme_charges_write_retry pagarme_charges_write_update_card pagarme_charges_write_update_due_date pagarme_charges_write_update_payment_method pagarme_customers_get pagarme_customers_get_address pagarme_customers_list pagarme_customers_list_addresses pagarme_customers_write_create pagarme_customers_write_create_address pagarme_customers_write_delete_address pagarme_customers_write_update pagarme_customers_write_update_address pagarme_invoices_cancel pagarme_invoices_get pagarme_invoices_list pagarme_invoices_write pagarme_legacy_balance pagarme_legacy_get_transaction pagarme_legacy_list_customers pagarme_legacy_list_payables pagarme_legacy_list_plans pagarme_legacy_list_recipients pagarme_legacy_list_subscriptions pagarme_legacy_list_transactions pagarme_legacy_list_transfers pagarme_list_accounts pagarme_orders_get pagarme_orders_get_many pagarme_orders_list pagarme_orders_write_close pagarme_orders_write_create pagarme_orders_write_update pagarme_payables_get pagarme_payables_list pagarme_plans_delete pagarme_plans_get pagarme_plans_list pagarme_plans_write_create pagarme_plans_write_update pagarme_recipients_anticipation_limits pagarme_recipients_anticipations pagarme_recipients_balance pagarme_recipients_default pagarme_recipients_get pagarme_recipients_list pagarme_recipients_transfers pagarme_recipients_withdrawals pagarme_recipients_write_create pagarme_recipients_write_create_anticipation pagarme_recipients_write_create_withdrawal pagarme_recipients_write_update pagarme_recipients_write_update_bank_account pagarme_subscriptions_cancel pagarme_subscriptions_cycles pagarme_subscriptions_get pagarme_subscriptions_items pagarme_subscriptions_list pagarme_subscriptions_usages pagarme_subscriptions_write_add_item pagarme_subscriptions_write_add_usage pagarme_subscriptions_write_create pagarme_subscriptions_write_update_billing_date pagarme_subscriptions_write_update_card pagarme_subscriptions_write_update_payment_method pagarme_transfers_get pagarme_transfers_list pagarme_transfers_write report_bug show_version toolkit_info

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	86/86	✓
has a description	86/86	✓
description is substantive	86/86	✓
parameters are typed	86/86	✓
parameters are described	3/86	3/86

86 of 86 tools graded · 86 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.9.241

server version mcp-ai

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:49Z	ok_tools	200	724	2025-06-18
2026-08-12T05:35:03Z	ok_tools	200	3986	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.mcp-dir/pagarme-mcp.svg)](https://robinsaige.com/s/io.github.mcp-dir/pagarme-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview