mcpship: check and publish MCP servers
NPM · MCPSHIP
Checks a remote MCP server against the Claude directory rules and guides its publication.
Available components
Last scanned (3 hours ago)
Scores higher than 39% of npm servers
Category Developer Tools
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 386 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 86 functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 8 Oct 26 39
First indexed and scored.
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 17 Oct 2026 · Analysed npm/mcpship@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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mcpship_check Check an MCP server against the Claude directory rules ~117
Tests a remote MCP server: OAuth discovery, PKCE and client registration, tool titles and annotations, instruction-free descriptions, and the listing (icon URL, pages, field lengths). Lists tools when MCPSHIP_TOKEN is set in the environment. Returns each rule as pass, fail, warn or skip, with a fix for every failure.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Folder that holds publish.json. Defaults to the folder the server was started in. |
| url | string | – | Server URL. Defaults to server_url in publish.json. |
No output schema declared.
No examples provided.
mcpship_done Record the directory submission ~69
Records in publish.json that the Claude directory form was submitted today. The directory has no public status API, so this is the only manually confirmed step.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| dir | string | – | Folder that holds publish.json. Defaults to the folder the server was started in. |
No output schema declared.
No examples provided.
mcpship_next Next publishing step ~71
Returns the first unfinished publishing step (check, npm, MCP Registry, plugin repo, submission text, directory) with the exact command or click for it. Reads the live state of every channel.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Folder that holds publish.json. Defaults to the folder the server was started in. |
No output schema declared.
No examples provided.
mcpship_packet Write the directory submission text ~69
Writes docs/directory/submission.md next to publish.json: the text for each step of the Claude directory form, in portal order. Fields missing from publish.json are marked MISSING.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Folder that holds publish.json. Defaults to the folder the server was started in. |
No output schema declared.
No examples provided.
mcpship_status Publishing status ~60
Returns the live state of npm, the MCP Registry, the Claude Code plugin repo and the Claude directory submission for the project in publish.json.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Folder that holds publish.json. Defaults to the folder the server was started in. |
No output schema declared.
No examples provided.
How do I install the mcpship: check and publish MCP servers server?
mcpship: check and publish MCP servers runs locally as an npm package, launched with npx -y mcpship. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcpship
claude mcp add emanueltns-mcpship -- npx -y mcpship
What is the mcpship: check and publish MCP servers server?
mcpship: check and publish MCP servers is listed in the public MCP registry as io.github.emanueltns/mcpship. Checks a remote MCP server against the Claude directory rules and guides its publication. This page covers its npm package (mcpship).
Is the mcpship: check and publish MCP servers server safe to use?
mcpship: check and publish MCP servers scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 mcpship: check and publish MCP servers server expose?
mcpship: check and publish MCP servers exposes 5 tools: mcpship_check, mcpship_next, mcpship_status, mcpship_packet, mcpship_done. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.
Is the mcpship: check and publish MCP servers server still maintained?
mcpship: check and publish MCP servers is still listed as active in the MCP registry. We last reached this channel on 17 October 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 mcpship: check and publish MCP servers server under?
mcpship: check and publish MCP servers declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.