Ext Ops Panel
Open dashboard
Comparison

OpenAPI Toolkit vs Austin Oaks Payload Rescue

OpenAPI Toolkit is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). Austin Oaks Payload Rescue is an MCP server published by freshypenguin.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOpenAPI ToolkitAustin Oaks Payload Rescue
Docker MCP Catalog Listed
Version: sha256:26234065b6a7
Forks (GitHub): 3
Pulls (Docker Hub): 43 755
Stars (Docker Hub): 1
Stars (GitHub): 18
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.2
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

OpenAPI Toolkit vs Austin Oaks Payload Rescue
FactOpenAPI ToolkitAustin Oaks Payload Rescue
Marketplaces that list it11
Stars (GitHub) (differs)18No figure on GitHub
Pulls (Docker Hub) (differs)43 755No figure on Docker Hub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/openapi)Remote server (ao-payload-rescue-production.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)5Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/lepoco/openapi.clientNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (3 days ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

OpenAPI Toolkit

In its own words, on Docker MCP Catalog:

Fetch, validate, and generate code or curl from any OpenAPI or Swagger spec - all from a single URL.

Austin Oaks Payload Rescue

In its own words, on Official MCP Registry:

Repair malformed JSON that fails a schema. Deterministic only; refuses to guess; signed receipt.

How to run each

OpenAPI Toolkit As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio openapi -- docker run -i --rm mcp/openapi

Austin Oaks Payload Rescue As a remote MCP server

Claude Code
claude mcp add --transport http ao-payload-rescue https://ao-payload-rescue-production.up.railway.app/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Austin Oaks Payload Rescue has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Austin Oaks Payload Rescue publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Austin Oaks Payload Rescue publish no settings it asks for, so we do not compare settings.

What it can do: OpenAPI Toolkit · What it can do: Austin Oaks Payload Rescue · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built