Sam's Club MCP

The materials indicate no separate API key or environment variables are required, which reduces developer-secret exposure. However, its stated function is to connect an account and access balances, statements, cards, and investments, so real-world use will likely involve user authorization tokens or sessions, making this a sensitive credential context that warrants careful scope and token handling.

It is known to connect to the declared remote endpoint api.mcp.ai. Based on the functionality description, user queries and related account/financial data will likely be transmitted through that endpoint. There is no evidence of exfiltration to unknown or unrelated domains, but the sensitivity of financial data means transmission scope and server-side handling should be reviewed.

The system checks indicate that this MCP tool executes code or starts a local process, which is a standard capability for this class of tools. The available materials do not show requests for system privileges beyond its stated purpose, nor any suspicious execution chain, so this is rated as caution rather than risk.

Per the description, its primary data access surface is the linked account’s financial data, including balances, statements, cards, and investment information; this is highly sensitive data. The materials do not show additional local file read/write needs or broad system resource access, nor obvious over-authorization, but it should still be used with minimal data scope.

The source is an official registry entry with publicly available source code and updates within the last year, all of which are clear risk-reducing factors. However, the repository lacks a declared license, has no README, and has very low community star count, which limits audit context and community validation. Overall, supply-chain risk does not appear high, but source and dependency review is still advisable.