mu-mcp

The server does not use `eval` or exhibit obfuscation. Secrets are handled via environment variables. The primary potential risk involves file handling: the `chat` tool accepts absolute file paths (`files`, `images`) as arguments. While this is expected functionality for an agent to provide context, it implies trust in the calling MCP client (Claude Desktop) to provide valid, non-malicious, and appropriately sandboxed paths. Path traversal within the context of arbitrary user-provided file paths could lead to unintended file disclosure if the calling client were compromised, though the server itself doesn't actively sanitize these paths beyond basic file existence checks. Conversation storage uses UUIDs for file names, mitigating direct path traversal for its own storage.