# HTTP 451 unavailable-legal

> HTTP 451 unavailable-legal is an MCP server for legal and government. Remote MCP endpoint that returns the meaning of HTTP status code 451. 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-451
- **Categories:** [legal and government](https://ai-powered.com/categories/legal-and-government), [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

This is a small remote MCP server published under the registry name io.github.sadri-dridi/http-451. Its registry description is a single line, "Meaning of HTTP 451", and it is reached over streamable HTTP at a hosted Cloudflare Workers URL rather than installed as a package.

It belongs to a repository of single-purpose public MCP servers meant for autonomous clients. Sibling entries cover things like ID layouts and calendar checks, and the README also lists a group of endpoints that route agents to a separate advertising service. The README gives no tool names, parameters or response format for this particular server.

It may suit developers who want to see how a minimal remote MCP endpoint behaves, or who want an agent to look up what an HTTP status means.

## Features

- **Single-purpose lookup:** Registry entry describes it as explaining the meaning of HTTP 451.
- **Remote streamable HTTP:** Runs as a hosted endpoint, so no local package install is needed.
- **Registry-named server:** Published under the official MCP registry name io.github.sadri-dridi/http-451.
- **Part of a utility collection:** Lives in a repository of many small named MCP servers for autonomous clients.

## Good for

- Letting an agent look up what HTTP 451 means
- Testing an MCP client against a minimal remote streamable-HTTP server
- Exploring how small single-purpose MCP servers are published in the registry

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### What does this server do?

Its registry description says it provides the meaning of HTTP 451.

### How do I connect to it?

It is a remote server using the streamable-http transport at the URL listed in the registry entry; there is no installable package.

### Does it list its tools?

No tool names or schemas are documented in the README or registry entry.

### Is it part of a larger project?

Yes, it sits in the named-mcp-utilities repository, which lists many other small MCP servers.

### How do I add HTTP 451 unavailable-legal to Claude Code?

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

### What are the best alternatives to HTTP 451 unavailable-legal?

The closest alternatives to HTTP 451 unavailable-legal are HTTP 401 unauthorized, HTTP 501 not-implemented, HTTP 431 header-fields-too-large, HTTP 405 method-not-allowed and HTTP 422 unprocessable.

## 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 401 unauthorized](https://ai-powered.com/mcp/http-401-unauthorized): HTTP 401 unauthorized is an MCP server for developer tools.
- [HTTP 501 not-implemented](https://ai-powered.com/mcp/http-501-not-implemented): HTTP 501 not-implemented 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 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 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable is an MCP server for developer tools.
- [HTTP 302 found](https://ai-powered.com/mcp/http-302-found): HTTP 302 found is an MCP server for developer tools.
- [HTTP 400 bad-request](https://ai-powered.com/mcp/http-400-bad-request): HTTP 400 bad-request is an MCP server for developer tools.
- [HTTP 410 gone](https://ai-powered.com/mcp/http-410-gone): HTTP 410 gone is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-451-unavailable-legal
