Skip to content
MCP server

HTTP 429 too-many-requests

Remote MCP endpoint that returns the meaning of HTTP status code 429

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About HTTP 429 too-many-requests

HTTP 429 too-many-requests is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

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.

Install

Run in a terminal

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

Add to Settings → Connectors → Add custom connector

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

Add to ~/.cursor/mcp.json

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

Add to .vscode/mcp.json

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

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

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

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

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

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

What it does

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

HTTP 429 too-many-requests 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.

How AIPoweredBot checks servers