Ext Ops Panel
Open dashboard
Comparison

OpenAPI Toolkit vs HTTP

OpenAPI Toolkit is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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 ToolkitHTTP
Docker MCP Catalog Listed
Version: sha256:26234065b6a7
Forks (GitHub): 3
Pulls (Docker Hub): 43 542
Stars (Docker Hub): 1
Stars (GitHub): 18
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 187
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 1
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 HTTP
FactOpenAPI ToolkitHTTP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)18 (better)1 (worse)
Pulls (Docker Hub) (differs)43 542No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/openapi)On your machine (@abhishekmcp/http)
Transportstdiostdio
Tools it declares (differs)5Not published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/lepoco/openapi.clientgithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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.

HTTP

In its own words, on Official MCP Registry:

HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.

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

HTTP As a local MCP server: npm package

Claude Code
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/http

Requires: HTTP_ALLOW_HOSTS

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

Tools each declares

The marketplaces of HTTP publish no list of tools, so we do not compare tools.

Settings each asks for

Only OpenAPI Toolkit asks for

  • MODE

Only HTTP asks for

  • HTTP_ALLOW_HOSTS
  • HTTP_WRITABLE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: OpenAPI Toolkit · What it can do: HTTP · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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