CLIO Hdf5

The material explicitly states that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential exposure risk appears low.

No remote endpoints or external hosts are declared, and the material does not indicate any need to send data to third-party services. Based on the available facts, there is no clear data egress path.

System checks indicate that this tool executes code. As an MCP server, it typically runs a local process to provide its capabilities. The material does not show unusually elevated permissions beyond its stated purpose, but local execution should still be treated with standard caution.

The description indicates access to HDF5 scientific data, implying it likely reads local HDF5 files or related data resources. The material does not specify write scope or broader file permissions; no clear overreach is visible, but data-reading capability still warrants least-privilege handling.

It comes from an official registry and has an auditable open-source repository with updates within the last year, both of which are clear risk-reducing signals. Although community stars are low and the license is not declared, its transparency is still better than closed-source or untrusted-origin tools, with no specific supply-chain red flags evident.