mcp-tomtom

The materials claim no credentials are required, but TomTom Search/Routing API usage would typically involve API credentials or a server-side proxy; the current information is insufficient to confirm truly credential-free operation. No explicit credential harvesting or abuse is described, but this inconsistency should be verified.

The stated functionality inherently requires access to TomTom search and routing services, so network egress is likely; however, the materials also state “no remote endpoints,” which conflicts with the description. There is no concrete red flag indicating exfiltration to unknown third parties, but query content should be assumed to be sent to TomTom or a proxy endpoint.

The system flags it as executes-code, meaning the MCP at least runs local code/processes, which is a normal capability for this class of tools. The materials do not show requests for unusual system privileges or dangerous actions unrelated to mapping queries, so this alone does not justify a high-risk rating.

The provided materials do not specify which local files, caches, or logs it may read or write, leaving its data-access scope opaque. Based on its function, it likely handles location, address, and route-query data; there is no explicit evidence of overbroad access, but the missing README prevents confirmation of least-privilege boundaries.

The source is auditable on GitHub and MIT-licensed, which are clear risk-reducing factors; however, it comes from a third-party registry, has only 0 stars, unknown maintenance status, and missing documentation, so supply-chain maturity and verifiability are limited. There is no sign of closed-source behavior or obvious malice, so this is caution rather than high risk.