HTTP status codes, explained.
Plus the tools to debug them.

A reference page for every status code from 100 to 511, ten fast developer tools, and an MCP server so your AI assistant can run the same checks.

Explore the tools Connect the MCP server

Status codes documented: 63
Free developer tools: 10
MCP tools for AI agents: 9
Sign-ups required: 0

Developer tools

Everything you need to debug a response

No sign-up, no tracking. Pick a tool and get an answer in seconds.

Network & HTTP

— Inspect any public URL through our edge proxy — nothing is stored.

Encode & decode

— Decode tokens, convert Base64 and tidy JSON.

Free test endpoints

— Public, CORS-open endpoints for test suites, monitors and demos.

Reference

Every status code, explained

Causes, client- and server-side fixes, an example exchange and a live URL that returns the exact code.

Browse all 63 codes

Model Context Protocol

Give your AI assistant these tools

The HttpStatus MCP server exposes nine read-only tools — status checks, redirect tracing, security-header and CORS audits, DNS, TLS, JWT decoding and test-endpoint generation — to Claude, Cursor and any MCP client. Remote, OAuth-protected, nothing to install.

Listed in the Claude directory
OAuth 2.1 with PKCE
Read-only and stateless
Streamable HTTP transport

Add to Claude Setup guide

Cursor / Claude Code config

{
  "mcpServers": {
    "httpstatus": {
      "url": "https://mcp.httpstatus.com/mcp"
    }
  }
}

Endpoint: https://mcp.httpstatus.com/mcp

HTTP status codes, explained.Plus the tools to debug them.