
This wraps http.cat, the site that serves up cat images representing HTTP status codes. It's a lighthearted tool for when you need a visual representation of 404s, 500s, or any other HTTP status. The server is part of Pipeworx's gateway ecosystem, which means you can either connect directly to this single endpoint or access it through their unified gateway alongside 673+ other data sources. It supports their ask_pipeworx natural language interface, so you can request status cat images conversationally rather than calling tools directly. Free to use, no authentication required. Mostly useful for adding some humor to error handling demos or documentation.
HTTP Cat MCP — wraps http.cat (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_status_cat | Get a cat image representing an HTTP status code. Provide the code (e.g., 200, 404, 500). Returns the image URL. |
list_codes | Browse all available HTTP status codes with descriptions and cat image URLs. Use to find the right code for your status or explore available options. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"httpcat": {
"url": "https://gateway.pipeworx.io/httpcat/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/httpcat/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Httpcat data" })
The gateway picks the right tool and fills the arguments automatically.
MIT