tiger-linear-mcp-server

The server correctly retrieves the LINEAR_API_KEY from environment variables, avoiding hardcoded secrets. Input validation is implemented using Zod schemas for all API endpoints, which helps mitigate common injection vulnerabilities. The core server functionality relies on the '@tigerdata/mcp-boilerplate' library, which is assumed to handle fundamental security practices for an MCP server (e.g., transport layer security if applicable for HTTP, robust error handling). No direct 'eval' or other easily exploitable malicious patterns were found in the provided code. Caching of users and projects is implemented, which is good for performance but does not directly impact security, other than reducing unnecessary external calls. For production deployment, additional security measures like network access control, HTTPS (if using HTTP transport), and robust authentication for the MCP server itself (beyond just the Linear API key) would be standard practice.