LeashIndex Get the report

Index / payments

io.github.codespar/mcp-mercado-pago

io-github-codespar-mcp-mercado-pago declares 30 capabilities across 30 tools, with 3 critical issues.

88/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package @codespar/mcp-mercado-pago@0.2.2 (published to npm as @codespar/mcp-mercado-pago, listed in the official MCP registry as io.github.codespar/mcp-mercado-pago 0.2.2), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · irreversible-uncapped · 5 of 30 tools

5 tools are classified as irreversible and declare no limit.

critical · no-revocation · All 30 tools

30 of 30 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · uncapped-spend · 4 of 30 tools

4 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 30 tools

30 of 30 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 30 tools

30 of 30 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 10 of 30 tools

10 tools can modify data and declare no limit.

low · uncapped-read · 15 of 30 tools

15 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
create_paymentpay inferred
get_paymentread inferred
search_paymentsread inferred
create_refundpay inferred
create_preferencewrite inferred
get_preferenceread inferred
create_customerwrite inferred
list_customersread inferred
get_payment_methodsread inferred
create_pix_paymentpay inferred
get_merchant_orderread inferred
get_balanceread inferred
create_subscriptionwrite inferred
get_subscriptionread inferred
cancel_subscriptiondelete inferred
create_card_tokenwrite inferred
get_payment_method_detailsread inferred
create_storewrite inferred
list_storesread inferred
create_poswrite inferred
update_subscriptionwrite inferred
oauth_token_exchangewrite assumed
create_advanced_paymentpay inferred
get_advanced_paymentread inferred
get_chargebackread inferred
upload_chargeback_evidencewrite inferred
get_identification_typesread inferred
get_payment_methods_by_siteread inferred
create_settlement_reportwrite inferred
search_merchant_ordersread inferred
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.