OAuth 2.1 wrapper for Grafana MCP server with Cognito authentication
This OAuth wrapper exposes 3 tools with critical definition gaps. Tool schemas are either missing entirely or severely underspecified. The 'mcp-proxy' tool accepts a generic object with no field documentation. Descriptions exist but lack actionable detail for LLM selection. No parameter descriptions, no output schemas, no error guidance. This server acts as a pass-through proxy rather than a well-defined tool interface.
Health check endpoint that returns server status and transport type
Proxy MCP requests to Grafana MCP server after OAuth token validation
OAuth 2.0 Protected Resource Metadata endpoint (RFC9728) that provides resource server configuration and supported scopes
mcp-proxy tool has no meaningful input schema. Input is declared as generic 'object' with description 'MCP request body (varies by MCP method)', LLMs cannot determine what fields are valid, required, or how to structure the payload.
No parameter descriptions on any tool. 'health' and 'oauth-protected-resource' appear to take no inputs, but this is not explicitly documented. 'mcp-proxy' input lacks field-level documentation entirely.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., does 'oauth-protected-resource' return scopes, endpoints, or both?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Tool naming lacks clarity. 'mcp-proxy' is a generic pass-through name that does not convey what the tool actually does. 'oauth-protected-resource' is a noun phrase, not a verb-noun action (should be 'get_oauth_resource_metadata' or similar).
No error handling guidance. If OAuth validation fails, token is expired, or Grafana is unreachable, the LLM receives no recovery instructions. Descriptions do not explain prerequisites (e.g., 'requires valid OAuth token') or failure modes.