CLIO Paraview

The material states that no keys or environment variables are required, and there is no request for API tokens, account credentials, or other sensitive authentication data, so credential exposure appears limited.

No remote endpoints or external service connections are declared in the available information; based on the stated facts, there is no explicit data egress path.

The system checks indicate that this tool has code execution capability; as an MCP server for ParaView, it is reasonable to infer that it may start local processes or invoke local visualization functionality. This is a normal capability for this class of tool, but its actual callable scope should still be reviewed.

As a scientific visualization service, it would typically need to read local data or result files for ParaView processing. The material does not specify a finer-grained data scope, and there is no evidence of overbroad access beyond its stated purpose, but local data access still warrants caution.

It comes from an official registry and has an open-source repository with updates in the past year, which are clear risk-reducing signals; however, the README is effectively absent, the license is not declared, and community adoption is very low (0 stars), leaving limited audit context and only moderate supply-chain transparency. Source and dependencies should be reviewed before use.