ship vs Hyperiux Vault
ship is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
ship is a plugin bundle for AI coding tools published by dilhanz. No marketplace we read lists it any more. Hyperiux Vault is an MCP server published by Hyperiux-Immersion-Labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Hyperiux Vault | |
|---|---|---|
| Community marketplace dilhanz/ship | Removed on 2026-10-26 Version: 5.28.0 Forks (GitHub): 3 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 535 Downloads/week (npm): 41 Forks (GitHub): 7 Stars (GitHub): 102 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 | shipno longer listed · | Hyperiux Vault |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | 102 |
| Forks (GitHub) (differs) | 3 | 7 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (hyperiux-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 25 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dilhanz/ship | github.com/hyperiux-immersion-labs/hyperiux-components |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ship
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Autonomous Development Orchestrator for Claude Code. Spec → Plan → Tasks → 100% Working App. Multi-agent pipeline with zero manual intervention.
-
Reusable Claude Code skills for disciplined software development.
-
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
-
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
-
Universal Claude Code workflow with specialized agents, skills, hooks, and mode commands for any software project. Includes orchestrator, code-reviewer, debugger, docs-writer…
-
Codex-native software specialist framework with tc-backed workflow discipline and Claude Copilot parity contracts.
What each says it does
ship
Feature-centric development framework for Claude Code — brainstorm, plan, build, and verify with structured workflows
Hyperiux Vault
Browse, inspect, and retrieve installable React and Next.js interaction effects from Hyperiux Vault.
How to run each
ship
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Hyperiux Vault As a local MCP server: npm package
claude mcp add --transport stdio hyperiux-mcp-server -- npx -y hyperiux-mcp-serverCommands 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: ship · What it can do: Hyperiux Vault · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.