HTTP 504 gateway-timeout
Remote MCP endpoint that returns the meaning of HTTP status 504 Gateway Timeout
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HTTP 504 gateway-timeout
HTTP 504 gateway-timeout 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 repository of small, single-purpose public MCP endpoints published under the sadri-dridi registry namespace. Its registry description is a single line: the meaning of HTTP 504. It is aimed at autonomous clients that want a quick lookup of a status code.
It runs as a remote service reachable over streamable HTTP on a Cloudflare Workers host, and no installable package is published. The README does not list the tool names or the exact response format.
The repository describes the collection as independently listed servers, each with its own intake. It also lists a set of promotional servers that route agents to an advertising service, so users should expect the host to be shared infrastructure for those.
Install
Run in a terminal
claude mcp add --transport http http-504 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"http-504": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"http-504": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"http-504": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"http-504": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- HTTP 504 lookup
- Provides an explanation of what the 504 Gateway Timeout status means.
- Remote streamable HTTP
- Connects to a hosted endpoint over streamable HTTP with no local install.
- Single-purpose design
- Each server in the repository covers one narrow topic under its own registry name.
- Registry listed
- Published in the official MCP registry as io.github.sadri-dridi/http-504.
Good for
- Let an AI client look up what a 504 error means while debugging
- Add a status-code reference to an agent's toolset
- Explain gateway timeout errors in automated incident notes
HTTP 504 gateway-timeout FAQ
How do I connect to this server?
Use the streamable HTTP remote URL given in the registry entry; no package is published.
What does it do?
The registry describes it as providing the meaning of HTTP 504.
Is it part of a larger project?
Yes, it belongs to the named-mcp-utilities repository, which hosts many small public MCP servers.
How do I add HTTP 504 gateway-timeout to Claude Code?
Run this command in your terminal: claude mcp add --transport http http-504 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-504/mcp
What are the best alternatives to HTTP 504 gateway-timeout?
The closest alternatives to HTTP 504 gateway-timeout are HTTP 502 bad-gateway, HTTP 503 unavailable, HTTP 505 http-version, HTTP 408 request-timeout and HTTP 501 not-implemented.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.