# HTTP 400 bad-request

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

## About

This is one of many small single-purpose endpoints published in a repository of named MCP utilities aimed at autonomous clients. The registry entry describes it only as giving the meaning of HTTP 400, the Bad Request status code.

It is reachable as a hosted streamable-http remote on a Cloudflare Workers address, with no installable package. Clients connect to the URL directly rather than running anything locally.

The repository README says each folder corresponds to one official registry name with its own intake, and it also lists a group of endpoints that route agents to an advertising service. The README does not document what tools this particular server exposes, so its behavior beyond the short registry description is unclear.

## Features

- **HTTP 400 lookup:** Provides an explanation of what the HTTP 400 status code means.
- **Remote streamable-http:** Served as a hosted endpoint using the streamable-http transport, so nothing needs installing.
- **Single-purpose design:** Part of a collection where each endpoint covers one narrow utility under its own registry name.

## Good for

- Let an AI agent look up what a 400 Bad Request response means
- Add a minimal reference endpoint to an MCP client for testing remote connections
- Explore how small named MCP utilities are registered and consumed by autonomous clients

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### What does this server do?

The registry entry describes it as giving the meaning of HTTP 400.

### How do I connect to it?

It is a remote server using the streamable-http transport at the URL given in its registry entry; no package is provided.

### Is it open source?

The code repository is public on GitHub, but the content does not state a license.

### Which tools does it expose?

The available information does not list specific tools.

### How do I add HTTP 400 bad-request to Claude Code?

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

### What are the best alternatives to HTTP 400 bad-request?

The closest alternatives to HTTP 400 bad-request are HTTP 404 not-found, HTTP 401 unauthorized, HTTP 502 bad-gateway, HTTP 451 unavailable-legal 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 404 not-found](https://ai-powered.com/mcp/http-404-not-found): HTTP 404 not-found 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 502 bad-gateway](https://ai-powered.com/mcp/http-502-bad-gateway): HTTP 502 bad-gateway 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.
- [HTTP 410 gone](https://ai-powered.com/mcp/http-410-gone): HTTP 410 gone 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 304 not-modified](https://ai-powered.com/mcp/http-304-not-modified): HTTP 304 not-modified is an MCP server for developer tools.
- [HTTP 403 forbidden](https://ai-powered.com/mcp/http-403-forbidden): HTTP 403 forbidden is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-400-bad-request
