Sentry

MCP server at https://mcp.sentry.dev/mcp (endpoint source: mcp_manifest)

0/2 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 6.0,
    "response_parseability": 5.0,
    "error_clarity": 8.0,
    "doc_quality": 8.0,
    "auth_simplicity": 7.0,
    "latency": 5.0,
    "consistency": 5.0
  },
  "issues": [
    "Auth wall: every request returned 401 Unauthorized with invalid_token error, so tool functionality could not be tested.",
    "Error responses are clean JSON-RPC-compatible with error_description, but the MCP spec expects no content or standard HTTP statuses for auth failures.",
    "No tool results, so token efficiency (during actual tool calls), first-try success, and response parseability cannot be fully assessed.",
    "The server responds to unauthenticated requests with 132ms and 82ms latency—low, but auth overhead is untested.",
    "Auth mechanism seems to require an access token (Sentry OAuth-like), but no token was provided, preventing tool discovery."
  ],
  "recommendations": [
    "Use a valid Sentry access token (e.g., from gettoken.sentry.dev or an API key) to test the actual MCP tools.",
    "Implement per-request rate limiting and ensure consistent error responses are strictly MCP-compliant (e.g., HTTP 401 with JSON-RPC error envelope).",
    "Document the auth flow clearly in the MCP manifest—agents need to know how to obtain a token before calling tools.",
    "If you observe 401 with 'invalid_token', the issue is not server-side; it's missing credentials. Ensure the agent supplies a token in the Authorization header."
  ],
  "pricing_normalized": {}
}