HTTP 501 not-implemented vs HTTP 502 bad-gateway
HTTP 501 not-implemented is an MCP server for developer tools. HTTP 502 bad-gateway is an MCP server for developer tools.
- HTTP 501 not-implemented is best for let an agent look up what http 501 means while debugging api responses.
- HTTP 502 bad-gateway is best for let an agent look up what a 502 bad gateway response means.
- What it is
- HTTP 501 not-implemented is an MCP server for developer tools.HTTP 502 bad-gateway is an MCP server for developer tools.
- Best for
- Let an agent look up what HTTP 501 means while debugging API responsesLet an agent look up what a 502 Bad Gateway response means
- Kind
- MCP serverMCP server
- Platforms
- APIAPI
- Runs
- RemotelyRemotely
- Open source
- 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 endpointLet 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
What HTTP 501 not-implemented 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.
What HTTP 502 bad-gateway does
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.
HTTP 501 not-implemented vs HTTP 502 bad-gateway: questions
What is the difference between HTTP 501 not-implemented and HTTP 502 bad-gateway?
HTTP 501 not-implemented is an MCP server for developer tools. HTTP 502 bad-gateway is an MCP server for developer tools.