mcp-nevent

The server correctly retrieves the Nevent JWT token from environment variables, preventing hardcoding of sensitive credentials. It acts as a wrapper around the Nevent API, meaning its security depends on the confidentiality of the provided JWT token and the robustness of the underlying Nevent API. No obvious 'eval', code obfuscation, or other malicious patterns were found. While the MCP SDK is expected to handle input schema validation, the internal tool handlers in `src/index.ts` use type assertions, which could be a minor concern if schema validation is bypassed. The communication with the Nevent API uses HTTPS.