io.github.us-all/openmetadata

The materials show it requires OPENMETADATA_HOST and OPENMETADATA_TOKEN, plus control variables such as OPENMETADATA_ALLOW_WRITE. The token is a sensitive credential; if exposed, it could be used to access the corresponding OpenMetadata instance, creating a normal credential-abuse risk.

Although no fixed remote endpoint is listed, the presence of OPENMETADATA_HOST indicates the tool connects to a user-specified OpenMetadata service and sends requests to it. Based on the provided materials, there is no clear red flag showing exfiltration to unrelated or unknown third-party endpoints.

The system checks indicate that this tool executes code/spawns a process, which is a normal characteristic of MCP tools. The current materials do not show requests for unusually high privileges or system actions unrelated to its stated functionality.

Based on the description, its functions cover metadata, lineage, search, data quality, and Data Contracts, implying access to related resources within OpenMetadata. OPENMETADATA_ALLOW_WRITE also suggests possible write operations. The available materials do not indicate broad local file access or obvious data-permission red flags beyond the stated purpose.

The source is the official registry and it has an auditable open-source repository with updates within the last year; these are clear positive signals. While the star count is low and the license is not declared, which adds some adoption and compliance uncertainty, this alone is not enough to raise it to high risk.