OpenAPI Toolkit vs VibeFix
OpenAPI Toolkit is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). VibeFix is an MCP server published by vibe-fixer.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
| Marketplace |   OpenAPI Toolkit |  VibeFix |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:26234065b6a7 Forks (GitHub): 3 Pulls (Docker Hub): 43 872 Stars (Docker Hub): 1 Stars (GitHub): 18 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | OpenAPI Toolkit | VibeFix |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 18 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 43 872 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | On your machine (mcp/openapi) | Remote server (vibe-fixer.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/lepoco/openapi.client | github.com/yos88da/vibefix-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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
Fetch, validate, and generate code or curl from any OpenAPI or Swagger spec - all from a single URL.
VibeFix
Signs up to your live app like a new person and shows what breaks. Every app gets one free check.
How to run each
OpenAPI Toolkit As a local MCP server: Docker image
claude mcp add --transport stdio openapi -- docker run -i --rm mcp/openapiVibeFix As a remote MCP server
claude mcp add --transport http vibefix https://vibe-fixer.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only VibeFix has a remote endpoint we check. How we check endpoints
Tools each declares
Only OpenAPI Toolkit has
create_csharp_snippetgenerate_curl_commandget_known_responsesget_list_of_operationsvalidate_document
Only VibeFix has
assess_broken_appcheck_live_appcheck_repair_statusconfirm_fixget_check_resultget_fix_optionslist_projects
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (VibeFix as of 2026-10-22). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of VibeFix publish no settings it asks for, so we do not compare settings.
What it can do: OpenAPI Toolkit · What it can do: VibeFix · 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.