finnhub-mcp-server

The server explicitly requires a Finnhub API key via environment variables and validates its presence. It uses Zod for input schema validation, which helps prevent malformed inputs. API requests are made using standard `fetch` to a known legitimate endpoint (`finnhub.io`), and includes robust error handling for API-specific issues like rate limits (429), invalid API key (401), and forbidden access (403). No 'eval' or other dynamic code execution from untrusted input is observed. Response content is formatted using internal utilities, and long outputs are truncated to prevent excessive token usage, also reducing potential for large data injection issues.