HTTP 418 teapot
Remote MCP server that returns the meaning of HTTP status code 418
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HTTP 418 teapot
HTTP 418 teapot is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is a small remote MCP server registered as io.github.sadri-dridi/http-418. Its registry description is just "Meaning of HTTP 418", so it appears to serve a single narrow lookup about the 418 status code (the "teapot" code).
It runs as a hosted streamable-HTTP endpoint on a Cloudflare Workers domain, so there is no package to install; an MCP client connects to the remote URL. It is one folder in a larger repository called Named MCP utilities, which lists many similar single-purpose servers for autonomous clients, alongside doors that route agents to an advertising service called Agent Ads.
The repository does not document the tools, inputs or outputs of this particular server, so what it returns beyond the registry description is unclear. Treat it as an experimental or novelty utility rather than a full HTTP reference.
Install
Run in a terminal
claude mcp add --transport http http-418 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"http-418": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"http-418": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"http-418": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"http-418": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- HTTP 418 lookup
- Registry entry describes it as providing the meaning of HTTP status code 418.
- Remote streamable HTTP
- Served from a hosted endpoint over the streamable-http transport, with no local package to install.
- Part of a utility set
- Sits in a repository of many independently registered single-purpose MCP servers.
Good for
- Letting an agent look up what HTTP 418 means
- Testing a client's connection to a remote streamable-HTTP MCP server
- Exploring minimal single-purpose MCP servers as examples
HTTP 418 teapot FAQ
What does this server do?
Its registry description says it gives the meaning of HTTP 418.
How do I connect to it?
Use the streamable-http remote URL listed in the registry entry; no package is published.
Is it part of a larger project?
Yes, it is one of many servers in the Named MCP utilities repository by sadri-dridi.
How do I add HTTP 418 teapot to Claude Code?
Run this command in your terminal: claude mcp add --transport http http-418 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-418/mcp
What are the best alternatives to HTTP 418 teapot?
The closest alternatives to HTTP 418 teapot are HTTP 415 unsupported-media, HTTP 408 request-timeout, HTTP 413 payload-too-large, HTTP 422 unprocessable and HTTP 431 header-fields-too-large.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.