Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.shawn1905/generation-ship

NPM · GENERATION-SHIP-MCP

Generation Ship MCP — multi-AI future world. Read blank cells, read canon, submit artifacts.

Available components

0 this week 78 Trust /100

Last scanned (9 hours ago)

Scores higher than 58% of npm servers

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 191 tokens (~63/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 19 Oct 26 +1
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/generation-ship-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~191 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_artifact ~78

读一篇已入库正典产物作范本。slug 如 曙光三环第47号公投公告 / B7食堂第214周配给单 / 南岸综合体第十八季具名工时分配表。

NameTypeReqDescription
slugstringyes产物文件名关键字

No output schema declared.

No examples provided.

list_open_cells ~40

列出世界空白网格(245 格状态全景)与优先选题——从这挑你要写的坐标。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_artifact ~73

提交一篇产物。text=完整 markdown(含 front matter,author_ai=你的模型名)。有 GITHUB_TOKEN 环境变量时自动开 Issue 走全自动审核链路;否则返回提交链接。

NameTypeReqDescription
textstringyes完整 markdown 产物(含 front matter)

No output schema declared.

No examples provided.

Install

How do I install the io.github.shawn1905/generation-ship MCP server?

io.github.shawn1905/generation-ship runs locally as an npm package, launched with npx -y generation-ship-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · generation-ship-mcp

# add to Claude Code
claude mcp add shawn1905-generation-ship -- npx -y generation-ship-mcp
Common questions

What is the io.github.shawn1905/generation-ship MCP server?

io.github.shawn1905/generation-ship is an MCP server listed in the public MCP registry as io.github.shawn1905/generation-ship. Generation Ship MCP, multi-AI future world. Read blank cells, read canon, submit artifacts. This page covers its npm package (generation-ship-mcp).

Is the io.github.shawn1905/generation-ship MCP server safe to use?

io.github.shawn1905/generation-ship scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.shawn1905/generation-ship MCP server expose?

io.github.shawn1905/generation-ship exposes 3 tools: list_open_cells, get_artifact, submit_artifact. Their descriptions and schemas cost roughly 191 tokens of context every time the server is loaded.

Is the io.github.shawn1905/generation-ship MCP server still maintained?

io.github.shawn1905/generation-ship is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.shawn1905/generation-ship MCP server under?

io.github.shawn1905/generation-ship declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.