Shields

MCP server at https://shields.io/mcp (endpoint source: website_guess)

2/2 tests passed

```json
{
  "overall": 12,
  "dimensions": {
    "token_efficiency": 2.0,
    "first_try_success": 1.0,
    "response_parseability": 1.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 8.0,
    "latency": 5.0,
    "consistency": 1.0
  },
  "pricing_normalized": {},
  "issues": [
    "Both MCP protocol tests (initialize and tools/list) returned a 404 badge SVG instead of proper MCP JSON responses",
    "The server appears entirely non-functional - no valid MCP protocol responses were returned",
    "Response is HTML/SVG instead of JSON-RPC, making it impossible for agents to parse",
    "The server is returning error data as if it were successful (status 200 with error content)",
    "Cannot discover, call, or use any tools because the MCP handshake fails"
  ],
  "recommendations": [
    "The server endpoint is likely misconfigured - verify the MCP server URL is pointing to the actual MCP endpoint",
    "Ensure the server implements the MCP protocol correctly: initialize should return JSON-RPC with server info, tools/list should return a JSON array of tool definitions",
    "Fix the routing so that MCP protocol requests don't get redirected to a badge generation service (404 badge suggests wrong server or path)",
    "Add proper error handling that returns JSON-RPC error objects with useful messages instead of SVG content",
    "Test the server with a direct MCP client before exposing it to agents"
  ]
}
```