oh-no-mcp-server

The server's core functionality involves read-only access to the file system to gather code content based on paths provided by an MCP client. It does not contain `eval()` or similar dangerous functions in its runtime logic (an `exec` call is present in the test suite for module execution testing only). No hardcoded secrets were found. During directory scans, it explicitly excludes common sensitive directories like `.git` and `node_modules`. The primary security consideration is the potential for an untrusted client or LLM to request the reading of arbitrary local files if the MCP client environment (e.g., Claude Desktop) does not adequately sandbox or validate paths. The server itself does not perform file writing; it only prepares prompts that may instruct the LLM to write reports to a specified `output_path`, placing the responsibility for the actual write operation and its security implications on the LLM's client environment.