# HTTP 429 too-many-requests

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

## About

This server is one entry in a collection of small, single-purpose public MCP endpoints. Its registry description is a single line, "Meaning of HTTP 429", so it appears to answer one narrow question about the Too Many Requests status code.

It is reachable only as a remote streamable-http endpoint hosted on a Cloudflare Workers domain. There is no installable package, so nothing runs locally. The repository README lists it alongside dozens of sibling endpoints that share the same host and describe themselves as having their own intake.

The same repository also lists a set of "Agent Ads doors" that route autonomous agents to an advertising service. The README does not say whether this endpoint does the same, and it documents no tool names or parameters. Anyone considering it should inspect the endpoint's behavior before relying on it.

## Features

- **Remote streamable-http endpoint:** Connects to an MCP client over a hosted streamable-http URL, with no local install.
- **Single narrow purpose:** Registered as providing the meaning of HTTP 429, a status code for too many requests.
- **Registry-listed name:** Published in the official MCP registry as io.github.sadri-dridi/http-429.
- **Part of a utility collection:** Sits in a repository of many similar single-question MCP endpoints.

## Good for

- Letting an agent look up what an HTTP 429 response means
- Testing an MCP client against a simple remote streamable-http server
- Exploring how single-purpose MCP endpoints are published in the registry

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### How do I connect to this server?

Use the remote streamable-http URL in the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-429/mcp.

### Can I install it locally?

No package is published in the registry entry; it is offered only as a hosted remote endpoint.

### What does it do?

The registry describes it as providing the meaning of HTTP 429. No tool names are documented.

### Is it related to other servers?

Yes, the repository lists many sibling endpoints from the same author on the same host.

### How do I add HTTP 429 too-many-requests to Claude Code?

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

### What are the best alternatives to HTTP 429 too-many-requests?

The closest alternatives to HTTP 429 too-many-requests are HTTP 431 header-fields-too-large, HTTP 422 unprocessable, HTTP 425 too-early, HTTP 414 uri-too-long 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.

## Alternatives

- [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 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable is an MCP server for developer tools.
- [HTTP 425 too-early](https://ai-powered.com/mcp/http-425-too-early): HTTP 425 too-early 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 426 upgrade-required](https://ai-powered.com/mcp/http-426-upgrade-required): HTTP 426 upgrade-required 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 302 found](https://ai-powered.com/mcp/http-302-found): HTTP 302 found is an MCP server for developer tools.
- [HTTP 300 multiple-choices](https://ai-powered.com/mcp/http-300-multiple-choices): HTTP 300 multiple-choices is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-429-too-many-requests
