# Http Status Code Lookup — REST API endpoint `http-status-code-lookup`

Return the meaning, typical use case and fix for HTTP status codes. Look up one code (e.g. "404"), a class ("4xx"), or search by name or keyword ("too many requests"); filter by category.

- Category: network
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/http-status-code-lookup/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/http-status-code-lookup/
- Same tool on the other surface: https://findutils.com/mcp/http-status-code-lookup/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/http-status-code-lookup/execute \
  -H "Content-Type: application/json" \
  -d '{
    "query": "404"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/http-status-code-lookup
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Status code, class or keyword, e.g. "404", "5xx", "rate limit". Empty returns the whole table. |
| `category` | string (all \| 1xx Informational \| 2xx Success \| 3xx Redirection \| 4xx Client Error \| 5xx Server Error) | no | Limit results to one class. Default: `"all"`. |
| `limit` | integer | no | Maximum number of results (1-100). Default: `10`. |

Example arguments (verified):

```json
{
  "query": "404"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:http_status_code_lookup`. Full MCP reference: https://findutils.com/mcp/http-status-code-lookup/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt