All MCP servers

A remote MCP endpoint named HTTP 511 network-auth that, per its registry description, concerns the meaning of HTTP status 511.

HTTP 507 insufficient-storage

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 507 status code, described only as explaining the meaning of HTTP 507.

HTTP 505 http-version

io.github.sadri-dridi

A remote MCP endpoint whose stated purpose is explaining the meaning of the HTTP 505 status code.

HTTP 504 gateway-timeout

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 504 gateway-timeout status, with no documented tools or usage.

HTTP 503 unavailable

io.github.sadri-dridi

A remote MCP endpoint named HTTP 503 unavailable whose registry entry only states the meaning of HTTP 503.

HTTP 502 bad-gateway

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 502 status code, with no documented tools or capabilities.

HTTP 501 not-implemented

io.github.sadri-dridi

A remote MCP endpoint whose only stated purpose is explaining the meaning of the HTTP 501 status code.

HTTP 500 internal-error

io.github.sadri-dridi

A remote MCP endpoint named HTTP 500 internal-error that, per its registry description, only conveys the meaning of the HTTP 500 status code.

HTTP 451 unavailable-legal

io.github.sadri-dridi

A remote MCP endpoint named HTTP 451 unavailable-legal, described only as explaining the meaning of HTTP 451.

HTTP 431 header-fields-too-large

io.github.sadri-dridi

A remote MCP endpoint named for HTTP 431 header-fields-too-large, with no tools, authentication, or usage details declared.

HTTP 429 too-many-requests

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 429 status code, with no documented tools or usage details.

HTTP 428 precondition-required

io.github.sadri-dridi

A remote MCP endpoint named for HTTP 428 that, per its README, is one of many small public utility servers for autonomous clients.

HTTP 426 upgrade-required

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 426 status code, with no documented tools, authentication, or usage details.

HTTP 425 too-early

io.github.sadri-dridi

A remote MCP endpoint whose stated purpose is explaining the meaning of the HTTP 425 status code.

HTTP 422 unprocessable

io.github.sadri-dridi

A remote MCP endpoint named for HTTP 422 that, per its description, only states the meaning of that status code.

HTTP 418 teapot

io.github.sadri-dridi

A remote MCP endpoint named HTTP 418 teapot, described only as explaining the meaning of HTTP status 418.

HTTP 415 unsupported-media

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 415 status code, with no documented tools beyond that label.

HTTP 414 uri-too-long

io.github.sadri-dridi

A remote MCP endpoint that explains the meaning of the HTTP 414 URI Too Long status code.

HTTP 413 payload-too-large

io.github.sadri-dridi

A remote MCP endpoint named HTTP 413 payload-too-large, described only as explaining the meaning of the HTTP 413 status code.

HTTP 412 precondition-failed

io.github.sadri-dridi

A remote MCP endpoint named for HTTP 412 that, per its listing, appears to be a placeholder with no documented tools.

HTTP 410 gone

io.github.sadri-dridi

A remote MCP endpoint whose stated purpose is explaining the meaning of the HTTP 410 status code.

HTTP 409 conflict

io.github.sadri-dridi

A remote MCP endpoint that appears to explain the meaning of the HTTP 409 conflict status code.

HTTP 408 request-timeout

io.github.sadri-dridi

A remote MCP endpoint named for the HTTP 408 request-timeout status, with no documented tools or usage.

HTTP 406 not-acceptable

io.github.sadri-dridi

A remote MCP endpoint whose stated purpose is explaining the meaning of the HTTP 406 Not Acceptable status code.