Ext Ops Panel
Open dashboard
Comparison

pracht dev-mcp vs mcpship: check and publish MCP servers

pracht dev-mcp is an MCP server published by JoviDeCroock. Marketplaces we read that list it: 1 (Official MCP Registry). mcpship: check and publish MCP servers is an MCP server published by emanueltns. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacepracht dev-mcpmcpship: check and publish MCP servers
Official MCP Registry Listed
Version: 1.18.0
Downloads/month (npm): 3 478
Downloads/week (npm): 822
Forks (GitHub): 6
Stars (GitHub): 108
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 194
Downloads/week (npm): 52
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

pracht dev-mcp vs mcpship: check and publish MCP servers
Factpracht dev-mcpmcpship: check and publish MCP servers
Marketplaces that list it11
Stars (GitHub) (differs)108 (better)0 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last release (differs)2026-11-11Not published
Where it runs (differs)On your machine (@pracht/cli)On your machine (mcpship)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/jovidecroock/prachtgithub.com/emanueltns/mcpship
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-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

pracht dev-mcp

In its own words, on Official MCP Registry:

Inspect, verify, diff, and scaffold a pracht app's routes, API, and capabilities from its app graph.

mcpship: check and publish MCP servers

In its own words, on Official MCP Registry:

Checks a remote MCP server against the Claude directory rules and guides its publication.

How to run each

pracht dev-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pracht -- npx -y @pracht/cli dev-mcp

mcpship: check and publish MCP servers As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcpship -- npx -y mcpship mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: pracht dev-mcp · What it can do: mcpship: check and publish MCP servers · 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.

Where the data comes from: how the catalog is built