Troubleshooting with ErrLookup

Start from the failure class, watch the MCP server resolve a real error, or wire it into your own agent.

Failure class guides

Most production errors belong to a handful of failure classes. Each guide explains one from the mechanism up and links every documented occurrence:

• Connection failures: ECONNREFUSED, ECONNRESET, and friends
• DNS resolution errors: ENOTFOUND and getaddrinfo failures
• SSL/TLS and certificate errors
• Timeouts: ETIMEDOUT, deadlines, and hung requests
• HTTP status errors: handling 4xx and 5xx responses
• Authentication and authorization failures
• Parsing and encoding errors: unexpected token, malformed input

For error families the guides don't cover, the background articles distill common causes across every documented occurrence — and grow twice a day as the collector runs.

See it in action

opencode hits an AxiosError, asks the ErrLookup MCP server what it means, and applies the fix the library authors recommend.

Give your coding agent error superpowers

{
  "mcpServers": {
    "errlookup": {
      "command": "npx",
      "args": [
        "-y",
        "@standardbeagle/errlookup-mcp"
      ]
    }
  }
}

The MCP server caches the dataset locally: offline-capable, no API keys, answers search_error straight from disk.