# io.github.CloudCorpRecords/shipcheck (npm · @reneturcios/shipcheck)

Release verification: git tag, release, npm, MCP Registry, and GHCR must agree, or NO-GO.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `@reneturcios/shipcheck`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck)
- oci · `ghcr.io/cloudcorprecords/shipcheck`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-shipcheck/ghcr-io-cloudcorprecords-shipcheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-shipcheck/ghcr-io-cloudcorprecords-shipcheck)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/shipcheck`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 394 tokens (~131/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/shipcheck MCP server?

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

### Claude

```bash
claude mcp add cloudcorprecords-shipcheck -- npx -y @reneturcios/shipcheck
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-shipcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/shipcheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-shipcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/shipcheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-shipcheck -- npx -y @reneturcios/shipcheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-shipcheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/shipcheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-shipcheck --command npx --arg -y --arg @reneturcios/shipcheck
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-shipcheck:
    command: "npx"
    args: ["-y", "@reneturcios/shipcheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-shipcheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/shipcheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-shipcheck -t stdio -c npx -a -y @reneturcios/shipcheck
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-shipcheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/shipcheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-20 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 55)

First indexed and scored.

## MCP tools (3)

### `check_release` (~225 tokens)

Verify a GitHub release shipped consistently: git tag resolves to a real commit, package.json at the tag matches, GitHub release is published, npm has the version and points latest at it, the MCP Registry lists it as latest, and GHCR has the image tag. Returns a GO or NO-GO report with evidence per surface.

Input parameters:

- `npmPackage` (string): npm package name when it cannot be inferred from package.json at the tag
- `repo` (string, required): Repo in owner/repo form, e.g. CloudCorpRecords/greenlight
- `require` (array): Surfaces or groups to force as hard checks: npm, registry, ghcr, release, github
- `serverName` (string): MCP Registry server name, defaults to io.github.<Owner>/<repo>
- `skip` (array): Surfaces or groups to skip: npm, registry, ghcr, release, github
- `version` (string): Expected version, e.g. 0.15.1. Omit to read it from package.json on the default branch.

### `check_npm` (~87 tokens)

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.

Input parameters:

- `package` (string, required): npm package name, e.g. @reneturcios/greenlight
- `version` (string, required): Expected version, e.g. 0.15.1

### `check_registry` (~82 tokens)

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.

Input parameters:

- `serverName` (string, required): Registry server name, e.g. io.github.CloudCorpRecords/greenlight
- `version` (string, required): Expected version, e.g. 0.15.1

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck#diagnostics

## Score history

- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 55

## Common questions

### What is the io.github.CloudCorpRecords/shipcheck MCP server?

io.github.CloudCorpRecords/shipcheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/shipcheck. Release verification: git tag, release, npm, MCP Registry, and GHCR must agree, or NO-GO. This page covers its npm package (@reneturcios/shipcheck).

### Is the io.github.CloudCorpRecords/shipcheck MCP server safe to use?

io.github.CloudCorpRecords/shipcheck scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 io.github.CloudCorpRecords/shipcheck MCP server expose?

io.github.CloudCorpRecords/shipcheck exposes 3 tools: check_release, check_npm, check_registry. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/shipcheck MCP server still maintained?

io.github.CloudCorpRecords/shipcheck is still listed as active in the MCP registry. We last reached this channel on 23 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 io.github.CloudCorpRecords/shipcheck MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/shipcheck
- Socket report: https://socket.dev/npm/package/@reneturcios/shipcheck
- Repository: https://github.com/CloudCorpRecords/shipcheck
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-shipcheck/reneturcios-shipcheck