PluginBench
MCP Server
Active

HTTP 501 not-implemented MCP Server

io.github.sadri-dridi/http-501

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the HTTP 501 not-implemented MCP server?

Meaning of HTTP 501.

How to install HTTP 501 not-implemented

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "http-501": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-501/mcp"
    }
  }
}

Related MCP servers

Meaning of HTTP 502.

0
View repository →

Meaning of HTTP 503.

0
View repository →

Meaning of HTTP 504.

0
View repository →

Meaning of HTTP 505.

0
View repository →

Meaning of HTTP 511.

0
View repository →