io.github.CSOAI-ORG/api-docs-generator-ai-mcp

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

The declared remote endpoint host is 'none', and the materials do not describe sending user data to third-party services. Based on the available information, there is no explicit network egress path.

The objective checks mark this tool as executes-code, meaning it runs code/processes locally as an MCP tool. This is a normal property of such tools; no unusually dangerous system privileges are described, but it should still be treated with the standard caution for executable components.

The available materials do not state that it reads sensitive directories, writes to system locations, scans local files, or accesses additional resources. No data access request beyond its stated 'API docs generation' purpose is evident.

Positive factors include an official registry source, an auditable open-source repository, and updates within the last year. Points to watch are the missing README, undeclared license, and very low community adoption (0 stars), which reduce transparency and ecosystem validation but do not by themselves constitute a high-risk red flag.