io.github.cyanheads/cdc-health-mcp-server

It requires CDC_APP_TOKEN; this token is a sensitive credential and could be abused to access the related data service if exposed. MCP_LOG_LEVEL is not a sensitive secret. The materials do not show the credential being sent to unrelated third parties or any obvious misuse pattern.

It declares outbound access to the remote endpoint cdc.caseyjhand.com, which is a normal capability for a tool that queries public health data. The materials do not specify whether user prompts or context are transmitted, but query requests will likely be sent there; no unrelated or covert egress red flags are evident.

The system checks indicate that this MCP tool executes code or runs a local process, which is inherent to MCP servers. The available materials do not show requests for unusual system privileges or commands unrelated to its stated purpose, so there is no specific red flag justifying a high-risk rating.

The materials provide no README or detailed permission model, so it is unclear which local files or data it can read or write. Based on its type, it likely handles user queries and returned results, but there is no explicit indication of broad filesystem, system settings, or other excessive access.

The source is an official registry entry with an auditable open-source repository and updates within the last year, all of which are positive risk-reducing signals. Community adoption is low and the license is unspecified, which adds some uncertainty, but there are no supply-chain red flags such as closed source, unknown provenance, or clear abandonment.