io.github.purahmanian/google-trends-mcp

The material explicitly states that no keys or environment variables are required. There is no indication that users must provide account credentials, API tokens, or local sensitive authentication material, so credential exposure and abuse risk appears low.

Although no remote host is declared in the metadata, the tool’s stated purpose is to fetch Google Trends metrics, related queries, and trending searches, which by function likely requires outbound requests to relevant external services. The documentation does not disclose specific endpoints, transmitted content, or minimization behavior, so users should assume query contents may be sent to a third-party service.

The system flags this tool as executes-code, meaning it runs an MCP server process or related code locally. This is a normal capability for this class of tool; the available material does not show requests for unusual system privileges or execution behavior beyond its stated 'trends query' functionality.

The public material does not specify which local files, caches, or log locations it may read or write, so visibility into data access scope is limited. Based on the description, its core function appears to be processing user-supplied query parameters, and there is no clear evidence that it needs broad local data access or system modifications, but it should still be run with least privilege.

Positive factors include listing in the official registry, an auditable open-source repository, and updates within the last year. Points to watch are the nearly absent README, no declared license, and very low community adoption (0 stars), which reduce contextual auditability and ecosystem validation; however, based on the available facts, these support a caution rating rather than a high-risk one.