CLIO Ndp

The materials state that no keys or environment variables are required. No API tokens, account credentials, or other sensitive secrets are requested, so credential exposure appears low.

The tool is described as searching and discovering datasets across multiple sources, so network queries are likely in practice; however, no specific remote endpoints are declared, and the system checks show no known host. Because the destination and transmitted content are not transparent, some caution is warranted, but there is no explicit evidence of exfiltration to unrelated or suspicious endpoints.

The system flags executes-code, indicating the tool can run local code or processes. This is a common MCP capability and not, by itself, a high-risk signal, but it should still be run in a constrained environment with attention to what system capabilities it actually invokes.

The materials do not specify which local files or data resources it can read or write, so the access scope is not fully transparent. As an MCP service that can execute code, some local data access should be assumed by default, but there is no stated request for permissions clearly beyond its dataset search/discovery purpose.

The source is an official registry entry, with a public source repository and updates within the last year, providing auditability and signs of maintenance. Community stars are low and the license is undeclared, which limits maturity signals, but these do not amount to a high-risk red flag.