atproto-mcp

The server demonstrates strong security practices, including extensive use of Zod for input validation, reliance on environment variables for sensitive configurations (e.g., OAuth client secrets, AT Protocol passwords), and a dedicated `SecurityManager` for input/error sanitization and rate limiting. It avoids dangerous patterns like `eval` and `child_process.exec` in core server logic (uses `spawn` for internal CLI/health checks). The primary interaction model is over STDIN/STDOUT, reducing direct network attack surface for the MCP protocol itself. Potential risks, such as handling `ATPROTO_PASSWORD` in 'app-password' mode, are inherent to the chosen authentication method rather than flaws in the server's implementation. Overall, it's well-engineered for secure operation as a trusted bridge component.