# HTTP 412 precondition-failed

> HTTP 412 precondition-failed is an MCP server for developer tools. Remote MCP endpoint that returns the meaning of HTTP status 412 for AI clients. 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-412
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

This is a single-purpose remote MCP server whose registry entry says it provides the meaning of HTTP 412, the Precondition Failed status code. It is hosted at a Cloudflare Workers address and reached over streamable HTTP, so there is nothing to install locally.

It is one of many narrowly scoped endpoints in the sadri-dridi named-mcp-utilities repository. The README describes the collection as independently listed public MCP servers for autonomous clients, with each folder tied to one official registry name. Sibling entries cover other tiny lookups, such as calendar-year checks and identifier formats, and some entries route agents to an advertising service.

It is mainly useful for testing MCP clients or for agents that need a quick reference on a status code. The registry entry lists no tool names, so the exact tool interface is not documented.

## Features

- **Single-topic lookup:** Focused on explaining what HTTP 412 (Precondition Failed) means.
- **Remote streamable HTTP:** Served from a hosted URL over the streamable-http transport, with no package to install.
- **Registry-listed name:** Published under the official registry name io.github.sadri-dridi/http-412.
- **Part of a utility collection:** Sits alongside many other small named MCP endpoints in the same repository.

## Good for

- Letting an AI agent look up the meaning of HTTP 412 while debugging an API call
- Testing connectivity of an MCP client to a remote streamable-http server
- Exploring how tiny single-purpose MCP servers are registered and discovered

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to it?

Point an MCP client that supports streamable HTTP at the remote URL given in the registry entry; no local package is needed.

### What does it return?

The registry describes it as providing the meaning of HTTP 412. No specific tool names are listed.

### Is it part of a larger project?

Yes, it belongs to the named-mcp-utilities repository, which collects many small public MCP servers.

### How do I add HTTP 412 precondition-failed to Claude Code?

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

### What are the best alternatives to HTTP 412 precondition-failed?

The closest alternatives to HTTP 412 precondition-failed are HTTP 422 unprocessable, HTTP 413 payload-too-large, HTTP 428 precondition-required, HTTP 415 unsupported-media and HTTP 410 gone.

## 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 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable 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.
- [HTTP 428 precondition-required](https://ai-powered.com/mcp/http-428-precondition-required): HTTP 428 precondition-required is an open-source MCP server for developer tools.
- [HTTP 415 unsupported-media](https://ai-powered.com/mcp/http-415-unsupported-media): HTTP 415 unsupported-media 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.
- [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 414 uri-too-long](https://ai-powered.com/mcp/http-414-uri-too-long): HTTP 414 uri-too-long is an MCP server for developer tools.
- [HTTP 451 unavailable-legal](https://ai-powered.com/mcp/http-451-unavailable-legal): HTTP 451 unavailable-legal is an MCP server for legal and government.

---
Source: https://ai-powered.com/mcp/http-412-precondition-failed
