Ext Ops Panel
Open dashboard
Comparison

OpenAPI Schema vs Piping Toolset Engineering Data

OpenAPI Schema is an MCP server published by hannesj. Marketplaces we read that list it: 1 (Docker MCP Catalog). Piping Toolset Engineering Data is an MCP server published by pipingtoolset.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 SchemaPiping Toolset Engineering Data
Docker MCP Catalog Listed
Version: sha256:5da1c1870748
Forks (GitHub): 14
Pulls (Docker Hub): 32 911
Stars (Docker Hub): 7
Stars (GitHub): 50
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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 Schema vs Piping Toolset Engineering Data
FactOpenAPI SchemaPiping Toolset Engineering Data
Marketplaces that list it11
Stars (GitHub) (differs)50 (better)1 (worse)
Pulls (Docker Hub) (differs)32 911No figure on Docker Hub
Forks (GitHub) (differs)14 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/openapi-schema)Remote server (pipingtoolset.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/hannesj/mcp-openapi-schemagithub.com/pipingtoolset/pipingtoolset-claude
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-12
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 h 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 Schema

In its own words, on Docker MCP Catalog:

OpenAPI Schema Model Context Protocol Server.

Piping Toolset Engineering Data

In its own words, on Official MCP Registry:

Engineering code-table data with citations: standard, edition, table, row and column.

How to run each

OpenAPI Schema As a local MCP server: Docker image

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

Piping Toolset Engineering Data As a remote MCP server

Claude Code
claude mcp add --transport http data https://pipingtoolset.com/mcp

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

Only Piping Toolset Engineering Data has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Piping Toolset Engineering Data publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: OpenAPI Schema · What it can do: Piping Toolset Engineering Data · 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