Mercado Pago MCP

The materials state that no additional secrets or environment variables are required, and there is no explicit request for user API tokens, system credentials, or local long-lived keys. Note that the feature set involves linking a Mercado Pago/Open Finance account; while the exact auth flow is not described, the provided materials do not show a clear credential-harvesting or abuse red flag.

The tool connects to the remote endpoint api.mcp.ai. Given the stated function—connecting a Mercado Pago account and retrieving balances, statements, cards, and investments—it is reasonable to infer that user queries and related financial data may transit through that endpoint. The destination is declared and not an unknown domain, so this is a standard network-egress caution item.

The system checks explicitly mark this tool as executes-code, indicating standard MCP capability to start local processes and execute code. The provided materials do not show requests for unusual system privileges or execution beyond its stated purpose, so this should be treated as a normal execution-surface caution rather than a high-risk issue.

The description indicates access to financial account data such as balances, statements, cards, and investments, all of which are sensitive business/personal data. There is no explicit claim of broad local file read/write access, but visibility into and processing of financial data itself should be treated as a significant data-access surface.

Positive signals include an official registry source, an open-source repository, and updates within the last year; these materially reduce supply-chain risk. However, the README is absent, the license is not declared, and community stars are 0, indicating weaker public documentation and ecosystem validation, so caution is more appropriate than a fully low-risk rating.