ags-api-mcp-server

The server employs several good security practices: environment variables for configuration, token masking in logs, PKCE for OAuth flows, OIDC token verification with JWKS, Helmet for HTTP security headers, and rate limiting (in V2). It adheres to a stateless architecture in V2, reducing session-related attack surfaces. A minor concern in V1's `StreamableHTTPTransport` is its `validateOrigin` which logs warnings but still allows non-localhost origins by default, which should be tightened for production outside of specific local scenarios. Furthermore, while the server uses JSONPath expressions, care must be taken when exposing these to LLMs to prevent potential injection if user input directly influences the expression, although the current implementation doesn't appear to directly facilitate this risk.