HTTP 414 uri-too-long
Remote MCP endpoint that explains the meaning of HTTP status code 414 for agents
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HTTP 414 uri-too-long
HTTP 414 uri-too-long is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is one of a set of small, single-purpose MCP servers published under the sadri-dridi namespace. Each one is registered under its own official registry name, and this one is dedicated to HTTP 414, the "URI Too Long" response.
It runs as a hosted remote endpoint over streamable HTTP, so there is nothing to install: an MCP client connects to the registry-listed URL. The registry entry describes it only as giving the meaning of HTTP 414, and no individual tool names are published.
The parent repository, named-mcp-utilities, groups many similar narrow endpoints, plus a separate set of doors that route agents to an advertising service. Those are different products from this one. The repository describes the collection as aimed at autonomous clients.
Install
Run in a terminal
claude mcp add --transport http http-414 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"http-414": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"http-414": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"http-414": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"http-414": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- HTTP 414 explanation
- Provides the meaning of the HTTP 414 (URI Too Long) status code.
- Remote streamable HTTP
- Served from a hosted endpoint over streamable HTTP, with no local package to install.
- Own registry name
- Registered as io.github.sadri-dridi/http-414 with its own endpoint, separate from sibling servers.
Good for
- Let an agent look up what an HTTP 414 error means while debugging requests
- Give an MCP client a quick reference for the URI Too Long status code
- Test remote streamable HTTP MCP connections with a minimal endpoint
HTTP 414 uri-too-long FAQ
What does this MCP server do?
According to its registry entry, it provides the meaning of HTTP 414.
How do I connect to it?
Point an MCP client at the remote streamable HTTP URL listed in the registry entry; no package is installed.
Is it part of a larger project?
Yes, it is one of many small servers in the sadri-dridi named-mcp-utilities repository, each registered under its own name.
How do I add HTTP 414 uri-too-long to Claude Code?
Run this command in your terminal: claude mcp add --transport http http-414 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-414/mcp
What are the best alternatives to HTTP 414 uri-too-long?
The closest alternatives to HTTP 414 uri-too-long are HTTP 431 header-fields-too-large, HTTP 413 payload-too-large, HTTP 429 too-many-requests, HTTP 410 gone and HTTP 404 not-found.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.