For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-21T02:19:27.823932+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://api.mcp.ai/p_pagarme",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-21T02:19:27.823932+00:00",
"registry_status": null,
"subject": {
"id": "io.github.mcp-dir/pagarme-mcp",
"kind": "mcp"
},
"tools": {
"names": [
"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"
],
"names_truncated": false,
"sha256": "fb1eb87c1bb450d5bd3a789bb79bb38ec1752837cacce6cf0942fa554663407a"
},
"tools_complete": true,
"tools_observed_at": "2026-10-21T02:19:27.823932+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology