io.github.cyanheads/openfoodfacts-mcp-server

The listed variables—OFF_BASE_URL, OFF_RATE_LIMIT_PRODUCT, OFF_RATE_LIMIT_SEARCH, and MCP_LOG_LEVEL—look more like configuration values than highly sensitive secrets; no API token, password, or OAuth credential is indicated. There is no clear credential-abuse red flag, but environment variables and logging settings should still be kept from unnecessary exposure.

The tool connects to the remote endpoint openfoodfacts.caseyjhand.com and, consistent with its stated function, would likely send barcodes, search terms, or comparison queries to that service. This is normal network egress, and the materials only show a single declared endpoint with no specific red flag indicating exfiltration to unknown or unrelated domains.

System checks indicate it executes code or starts a local process, which is a normal MCP tool characteristic. The provided materials do not show privilege escalation, arbitrary shell execution, or unrelated system capabilities, so this alone does not justify a high-risk rating.

The available materials do not state any need to read or write local files, databases, clipboard contents, browser sessions, or other sensitive resources; the description is limited to barcode lookup, nutrition search, and product comparison. Based on the known facts, there is no sign of overbroad data access.

The source is an official registry entry with an auditable open-source repository and updates within the last year, all of which materially reduce risk. Although community stars are low and the license is not stated, these add only limited uncertainty and do not amount to a supply-chain high-risk red flag.