Skip to content
MCP server

HTTP 413 payload-too-large

Remote MCP server that explains the meaning of HTTP status code 413

Install
Platforms
API
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About HTTP 413 payload-too-large

HTTP 413 payload-too-large is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

This server is one of a set of small single-purpose MCP endpoints published in the named-mcp-utilities repository. Its registry entry describes it only as giving the meaning of HTTP 413, the status code for a payload that is too large.

It runs as a remote streamable-http endpoint hosted on a Cloudflare Workers subdomain, so there is nothing to install locally; an MCP client connects to the URL given in the registry. The README presents the repository's servers as publicly listed utilities for autonomous clients, each with its own intake, but gives no tool list or usage details for this one.

It suits agents or developers who want a lightweight lookup for a single status code. Because the available documentation is minimal, the exact output and any tool names are not documented.

Install

Run in a terminal

claude mcp add --transport http http-413 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp

Add to Settings → Connectors → Add custom connector

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "http-413": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "http-413": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "http-413": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "http-413": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

What it does

HTTP 413 lookup
Provides the meaning of HTTP status 413 (payload too large) to connected MCP clients.
Remote streamable-http
Served from a hosted endpoint over streamable HTTP, with no package to install.
Single-purpose design
Focused on one narrow question, in line with the other small servers in the same repository.
Official registry name
Published under the io.github.sadri-dridi/http-413 registry name.

Good for

  • Letting an agent look up what a 413 response means while debugging an upload failure
  • Adding a minimal status-code reference to an MCP client's toolset
  • Testing connectivity to a remote streamable-http MCP server

HTTP 413 payload-too-large FAQ

What does this MCP server do?

Its registry description says it gives the meaning of HTTP 413.

How do I connect to it?

Point an MCP client at the streamable-http remote URL listed in the registry entry; no local package is published.

Is there anything to install?

No. The registry lists no packages, only a hosted remote endpoint.

Where is the source repository?

It is listed in the sadri-dridi/named-mcp-utilities repository on GitHub, alongside many similar servers.

How do I add HTTP 413 payload-too-large to Claude Code?

Run this command in your terminal: claude mcp add --transport http http-413 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-413/mcp

What are the best alternatives to HTTP 413 payload-too-large?

The closest alternatives to HTTP 413 payload-too-large are HTTP 431 header-fields-too-large, HTTP 414 uri-too-long, HTTP 415 unsupported-media, HTTP 429 too-many-requests and HTTP 412 precondition-failed.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers