OpenAPI Toolkit vs link.obfus/utility-grid
OpenAPI Toolkit is an MCP server published by lepoco. Marketplaces we read that list it: 1 (Docker MCP Catalog). link.obfus/utility-grid is an MCP server published by obfus.link. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  OpenAPI Toolkit |  link.obfus/utility-grid |
|---|---|---|
| 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: 1.0.1 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 | link.obfus/utility-grid |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 18 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 43 542 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/openapi) | Remote server (obfus.link/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/subether-labs/obfus-link-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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.
link.obfus/utility-grid
31 deterministic tools: JSON→Zod, regex, JWT, curl→fetch, hashing, encoding, UUIDs, encrypted links
How to run each
OpenAPI Toolkit As a local MCP server: Docker image
claude mcp add --transport stdio openapi -- docker run -i --rm mcp/openapilink.obfus/utility-grid As a remote MCP server
claude mcp add --transport http utility-grid https://obfus.link/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of link.obfus/utility-grid publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of link.obfus/utility-grid publish no settings it asks for, so we do not compare settings.
What it can do: OpenAPI Toolkit · What it can do: link.obfus/utility-grid · 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.