mcpship: check and publish MCP servers vs Data Calgary
mcpship: check and publish MCP servers is an MCP server published by emanueltns. Marketplaces we read that list it: 1 (Official MCP Registry). Data Calgary is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  mcpship: check and publish MCP servers |  Data Calgary |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 109 Downloads/week (npm): 21 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.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 | mcpship: check and publish MCP servers | Data Calgary |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (mcpship) | Remote server (gateway.pipeworx.io/data-calgary/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/emanueltns/mcpship | github.com/pipeworx-io/mcp-data-calgary |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 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
mcpship: check and publish MCP servers
Checks a remote MCP server against the Claude directory rules and guides its publication.
Data Calgary
DataCalgary MCP — Calgary open data (data.calgary.ca, Socrata SODA API).
How to run each
mcpship: check and publish MCP servers As a local MCP server: npm package
claude mcp add --transport stdio mcpship -- npx -y mcpship mcpData Calgary As a remote MCP server
claude mcp add --transport http data-calgary https://gateway.pipeworx.io/data-calgary/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Data Calgary has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of mcpship: check and publish MCP servers publish no settings it asks for, so we do not compare settings.
What it can do: mcpship: check and publish MCP servers · What it can do: Data Calgary · Compare two other plugins
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.