PluginBench
MCP Server
Active

Whether an HTTP status is retryable MCP Server

io.github.sadri-dridi/retry-status-hint

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 Whether an HTTP status is retryable MCP server?

Whether an HTTP status is retryable

How to install Whether an HTTP status is retryable

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": {
    "retry-status-hint": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/retry-status-hint/mcp"
    }
  }
}

Related MCP servers

RFC errata id shape, value discarded

0
View repository →

RFC number shape

0
View repository →

RFC section number shape

0
View repository →

HTTP status class 1xx-5xx

0
View repository →

encoded-word charset token, input discarded

0
View repository →

RFC 3339 UTC stamp

0
View repository →