Shipcheck MCP server

by CloudCorpRecords·io.github.CloudCorpRecords/shipcheck·v0.2.0

Release verification for Node and Python: tag, npm, PyPI, Registry, and GHCR must agree, or NO-GO.

A92/100grade A

What users say

No reviews yet

Safety scan

A92/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Shipcheck yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

check_npm
Check one npm package surface: the version is published and dist-tags.latest points at it. Catches staged publishing holds, where a version exists in the publish pipeline but is not actually live.
check_pypi
Check one PyPI package surface: the version is published with files and it is the latest release. A package absent from PyPI reports as skipped, not failed, because many Python projects ship only through GitHub, GHCR or an npm wrapper.
check_registry
Check one MCP Registry surface: the server lists the version and marks it as the latest active version. Servers absent from the registry report as skipped, not failed.
check_release
Verify a GitHub release shipped consistently: git tag resolves to a real commit, package.json and the Python metadata (pyproject.toml, setup.cfg, setup.py) at the tag match, server.json matches when present, GitHub release is published, npm has the version and points latest at it (only when the repo has an npm package), PyPI has the version and points latest at it (only for Python projects, skippe

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings

Code scan12 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 90% of 48,273 servers
Tools: 4; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read

Release history: 2 versions in the registry since 2026-10-19, latest 2026-10-26, typically one every 6 days.

Runs npx -y @reneturcios/shipcheck on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add shipcheck -- npx -y @reneturcios/shipcheck

Is Shipcheck MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Shipcheck safety report
How do I install Shipcheck?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Shipcheck need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Shipcheck maintained?: The last commit was 7 days ago (2026-10-26). The latest release is v0.2.0.
How does Shipcheck compare with other MCP servers?: safety score 92/100 (higher than 90% of 48,273 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.