mcp-omnisearch

The server adheres to strong security practices: API keys are strictly read from environment variables, preventing hardcoding. Network requests are centralized through `http_json`, which includes robust error handling for common HTTP issues (401, 403, 429, 5xx), preventing direct API error leakage. Input validation and query sanitization are applied before passing requests to external providers. The GitHub integration specifically recommends creating a Personal Access Token with no scopes for public access only, demonstrating a defense-in-depth approach. There is no usage of `eval` or other dynamic code execution methods.