Skip to content
MCP server

HTTP 422 unprocessable

Remote MCP endpoint that explains what HTTP status code 422 means, for AI clients

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About HTTP 422 unprocessable

HTTP 422 unprocessable is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

This is a single-purpose remote MCP server hosted as a streamable-HTTP endpoint on a Cloudflare Workers domain. Its registry entry describes it only as giving the meaning of HTTP 422 (Unprocessable Entity), so it works as a tiny lookup utility for agents that need that one definition.

It belongs to a larger set of small, named MCP utilities published from the same GitHub repository. Each folder in that repo maps to one official registry name with its own endpoint, and the sibling entries cover other narrow checks such as ID layouts, calendar leap-year tests and sort-code formats. The repo also lists a group of Agent Ads entries that route agents to an advertising service.

There is no package to install; an MCP client connects directly to the remote URL. No tool names or parameters are documented in the available material.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-422/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "http-422": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-422/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Using several servers? Build one config file with the MCP config generator.

What it does

Single-purpose lookup
Returns the meaning of HTTP status code 422 for connected AI clients.
Remote streamable HTTP
Runs as a hosted endpoint over the streamable-http transport, so nothing needs to be installed locally.
Official registry name
Published under the registry name io.github.sadri-dridi/http-422 with its own dedicated endpoint.
Part of a utility family
Sits alongside many other narrowly scoped named MCP utilities in the same repository.

Good for

  • Let an agent quickly check what a 422 response means while debugging an API call
  • Test remote MCP connectivity with a minimal streamable-HTTP server
  • Provide a status-code reference to an autonomous client without a full documentation lookup

HTTP 422 unprocessable FAQ

What does this MCP server do?

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

How do I connect to it?

Point an MCP client at the remote streamable-http URL listed in the registry entry; no package is published.

Where does it come from?

It is one of the named MCP utilities in the sadri-dridi/named-mcp-utilities GitHub repository.

How do I add HTTP 422 unprocessable to Claude Code?

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

What are the best alternatives to HTTP 422 unprocessable?

The closest alternatives to HTTP 422 unprocessable are HTTP 429 too-many-requests, HTTP 425 too-early, HTTP 412 precondition-failed, HTTP 302 found and HTTP 426 upgrade-required.

Where this comes from

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

How AIPoweredBot checks servers