# HTTP 426 upgrade-required

> HTTP 426 upgrade-required is an MCP server for developer tools. Remote MCP endpoint that explains the meaning of HTTP status code 426. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Platforms:** API
- **Repository:** https://github.com/sadri-dridi/named-mcp-utilities
- **MCP Registry name:** io.github.sadri-dridi/http-426
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

This is one of many single-purpose remote MCP servers published in the same repository, each registered under its own name. This one is registered as io.github.sadri-dridi/http-426 and its registry description reads simply "Meaning of HTTP 426", referring to the Upgrade Required status code.

It is reached over streamable HTTP at a hosted endpoint on a Cloudflare Workers domain, so there is nothing to install locally. No package is published; an MCP client connects to the remote URL directly.

The repository describes the collection as public MCP servers aimed at autonomous clients, with each folder acting as its own intake. The README does not document the specific tools this server exposes, so details of its responses are not confirmed. The same repository also includes servers that route agents to an advertising service.

## Features

- **HTTP 426 lookup:** Registered to provide the meaning of HTTP status code 426, Upgrade Required.
- **Remote streamable HTTP:** Connects over a hosted streamable-http endpoint, with no local package to install.
- **Dedicated registry name:** Has its own official registry entry, io.github.sadri-dridi/http-426.
- **Part of a utility collection:** Sits alongside many other narrowly scoped MCP servers in the named-mcp-utilities repository.

## Good for

- Let an AI client look up what HTTP 426 means while debugging API responses
- Test connecting an MCP client to a remote streamable-http server
- Explore small single-purpose MCP endpoints for agent workflows

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http http-426 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "http-426": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "http-426": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "http-426": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "http-426": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp"
    }
  }
}
```

## FAQ

### What does this MCP server do?

According to its registry entry, it provides the meaning of HTTP 426.

### How do I connect to it?

Use the remote streamable-http URL listed in the registry entry; no package is published for local install.

### Does it list its tools?

No. The registry entry and README do not list specific tool names.

### Where is the source repository?

It is part of github.com/sadri-dridi/named-mcp-utilities.

### How do I add HTTP 426 upgrade-required to Claude Code?

Run this command in your terminal: claude mcp add --transport http http-426 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-426/mcp

### What are the best alternatives to HTTP 426 upgrade-required?

The closest alternatives to HTTP 426 upgrade-required are HTTP 425 too-early, HTTP 422 unprocessable, HTTP 431 header-fields-too-large, HTTP 429 too-many-requests and HTTP 406 not-acceptable.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [HTTP 425 too-early](https://ai-powered.com/mcp/http-425-too-early): HTTP 425 too-early is an MCP server for developer tools.
- [HTTP 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable is an MCP server for developer tools.
- [HTTP 431 header-fields-too-large](https://ai-powered.com/mcp/http-431-header-fields-too-large): HTTP 431 header-fields-too-large is an MCP server for developer tools.
- [HTTP 429 too-many-requests](https://ai-powered.com/mcp/http-429-too-many-requests): HTTP 429 too-many-requests is an MCP server for developer tools.
- [HTTP 406 not-acceptable](https://ai-powered.com/mcp/http-406-not-acceptable): HTTP 406 not-acceptable is an MCP server for developer tools.
- [HTTP 405 method-not-allowed](https://ai-powered.com/mcp/http-405-method-not-allowed): HTTP 405 method-not-allowed is an open-source MCP server for developer tools.
- [HTTP 401 unauthorized](https://ai-powered.com/mcp/http-401-unauthorized): HTTP 401 unauthorized is an MCP server for developer tools.
- [HTTP 413 payload-too-large](https://ai-powered.com/mcp/http-413-payload-too-large): HTTP 413 payload-too-large is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-426-upgrade-required
