CLIO Jarvis

The materials state that no keys or environment variables are required, and there is no indication of API tokens, account credentials, or other sensitive authentication data being requested, so credential exposure appears low.

No remote endpoint host is declared, and the materials do not describe sending user data to external services; based on the available facts, there is no clear outbound data path.

The system flags executes-code, indicating the tool can execute code locally or start processes on the host. This is a normal but sensitive capability for an MCP tool, so its practical execution scope and least-privilege operation should be reviewed.

The description points to HPC pipeline management, which commonly involves reading/writing local projects, job configurations, or outputs. There is no concrete evidence of overbroad access, but given its code-execution capability, the local data-access boundary warrants caution.

The tool is distributed via an official registry and has an auditable open-source repository with updates within the last year; these are strong positive signals. While the low star count and unspecified license add some adoption and compliance uncertainty, they are not enough on their own to raise this to high risk.