CLIO Geo

The materials explicitly state that no keys or environment variables are required. No API tokens, cloud credentials, or third-party account access are indicated, so credential leakage and abuse exposure appears low.

Although no remote endpoint is declared, the feature description includes 'basemaps', which commonly may involve fetching map resources. The materials do not clarify whether operation is fully offline or which data sources are used. There is no explicit evidence of exfiltration to unknown endpoints, but the network behavior is underdocumented and should be checked in implementation.

System checks indicate that this MCP tool executes code/spawns processes, which is a normal capability for this class of tools. Given its purpose of rendering map images, it likely performs local graphics or data processing; the materials do not show requests for extra system privileges unrelated to its stated function.

By function, the tool may need to read user-supplied GeoJSON data and write rendered map images; this is normal data access for its purpose. The materials do not indicate scanning unrelated directories, collecting extra local data, or requesting excessive permissions, but the documentation is sparse, so restricting the working directory is advisable to verify actual access scope.

The source is an official registry entry with a public source repository and updates within the last year, providing auditability and some maintenance signals that lower supply-chain risk. Community adoption is low and the license is unspecified, which limits ecosystem validation, but these factors alone do not constitute a high-risk red flag.