mcpso

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

The materials state that there is no remote host endpoint. There is no stated need to contact external services or send user data to third parties; based on current facts, no explicit egress path is identified.

The system objectively flags it as executes-code, meaning it can execute code or processes locally. This is a common MCP/tool capability and not high risk by itself, but the lack of README and permission details warrants cautious use in a constrained environment.

The third-party description only says it is a 'directory for Awesome MCP Servers' and does not specify what local files, directories, or data resources it can access. The materials are insufficient to confirm actual data access boundaries, so least-privilege controls are advisable.

The source is an open-source GitHub repository with a clear Apache-2.0 license and about 2k stars, providing positive evidence of auditability and community adoption. The main limitation is sparse README/maintenance information, but that alone does not justify a high-risk rating.