HTTP 501 not-implemented
Remote MCP endpoint that returns the meaning of HTTP status code 501 for agents
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HTTP 501 not-implemented
HTTP 501 not-implemented is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP server registered as io.github.sadri-dridi/http-501. Its registry description says it provides the meaning of HTTP 501, the Not Implemented status code. It is reached over a streamable-http endpoint hosted on a Cloudflare Workers domain, so there is nothing to install locally.
It belongs to a repository called Named MCP utilities, which lists many small public MCP servers aimed at autonomous clients. Each one has its own registry name and its own endpoint. The same repository also lists a set of servers that route agents to an advertising service, so the endpoint may be part of that broader promotional setup.
The registry entry does not list any specific tools, parameters or output formats, so the exact behaviour is best checked by connecting a client to the endpoint.
Install
Run in a terminal
claude mcp add --transport http http-501 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"http-501": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"http-501": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"http-501": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"http-501": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- HTTP 501 lookup
- Exposes the meaning of the HTTP 501 Not Implemented status code to MCP clients.
- Remote streamable-http
- Served from a hosted URL over the streamable-http transport, with no local package to install.
- Dedicated registry name
- Registered under its own official registry name, io.github.sadri-dridi/http-501.
- Part of a utility set
- One of many small named MCP servers kept in the same repository.
Good for
- Let an agent look up what HTTP 501 means while debugging API responses
- Test a client's connection to a remote streamable-http MCP server
- Use as a minimal example of a single-purpose MCP endpoint
HTTP 501 not-implemented FAQ
What does this server do?
According to its registry entry, it provides the meaning of HTTP 501.
How do I connect to it?
Point an MCP client at the streamable-http remote URL given in the registry entry. No package is published for local install.
Where is the source?
The repository is sadri-dridi/named-mcp-utilities on GitHub, which lists many similar servers.
How do I add HTTP 501 not-implemented to Claude Code?
Run this command in your terminal: claude mcp add --transport http http-501 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp
What are the best alternatives to HTTP 501 not-implemented?
The closest alternatives to HTTP 501 not-implemented are HTTP 503 unavailable, HTTP 505 http-version, HTTP 401 unauthorized, HTTP 500 internal-error and HTTP 451 unavailable-legal.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.