# HTTP 502 bad-gateway

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

## About

This is a single-purpose remote MCP endpoint, served over streamable HTTP, whose registry description says it provides the meaning of HTTP 502 (Bad Gateway). It is one entry in a collection of small, separately registered utility servers published from the same repository.

There is nothing to install: the registry lists no packages, only a hosted remote URL on a Cloudflare Workers domain. An MCP-capable client connects to that URL directly. The repository README describes the collection as independently listed public MCP servers for autonomous clients, each with its own intake.

The README does not document the individual tools this server exposes, so what a call returns beyond the status-code explanation is unclear. The repository also promotes related servers that route agents to an advertising service, so users should be aware of that commercial context.

## Features

- **HTTP 502 meaning:** Provides an explanation of what the HTTP 502 status code means.
- **Remote streamable HTTP:** Runs as a hosted endpoint reachable over the streamable-http transport, with no local install.
- **Official registry name:** Registered as io.github.sadri-dridi/http-502 in the MCP registry.
- **Part of a utility set:** Listed alongside many other tiny single-purpose MCP servers in the same repository.

## Good for

- Let an agent look up what a 502 Bad Gateway response means
- Test connecting an MCP client to a minimal remote server
- Explain gateway errors while debugging HTTP failures

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to this server?

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

### What does it do?

The registry describes it as providing the meaning of HTTP 502.

### Is there a local package to install?

No. The registry entry lists no packages, only a hosted remote endpoint.

### How do I add HTTP 502 bad-gateway to Claude Code?

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

### What are the best alternatives to HTTP 502 bad-gateway?

The closest alternatives to HTTP 502 bad-gateway are HTTP 501 not-implemented, HTTP 503 unavailable, HTTP 504 gateway-timeout, HTTP 302 found and HTTP 505 http-version.

## 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 501 not-implemented](https://ai-powered.com/mcp/http-501-not-implemented): HTTP 501 not-implemented is an MCP server for developer tools.
- [HTTP 503 unavailable](https://ai-powered.com/mcp/http-503-unavailable): HTTP 503 unavailable is an MCP server for developer tools.
- [HTTP 504 gateway-timeout](https://ai-powered.com/mcp/http-504-gateway-timeout): HTTP 504 gateway-timeout 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 505 http-version](https://ai-powered.com/mcp/http-505-http-version): HTTP 505 http-version is an MCP server for developer tools.
- [HTTP 500 internal-error](https://ai-powered.com/mcp/http-500-internal-error): HTTP 500 internal-error 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 401 unauthorized](https://ai-powered.com/mcp/http-401-unauthorized): HTTP 401 unauthorized is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-502-bad-gateway
