Skip to content

MCP servers › io.github.sigship › sigship

MCP server · registry snapshot 2026-11-12 · last checked 2026-11-14

sigship MCP server

Registry name io.github.sigship/sigship

by sigship · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗

Go/no-go check for AI-built apps. Finds production problems locally and returns fixes. — the publisher's description

9 of 9 record checks metversion 0.4.0HTMLMITstandard input/output

Summary

io.github.sigship/sigship is a local MCP server listed in the official MCP registry at version 0.4.0, under the namespace of the GitHub account sigship. Its linked repository, github.com/sigship/sigship, belongs to the same GitHub account.

Record checks

9 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #2,014 of 20,610 packages by monthly downloads, tied with 3 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • #432 of 1,244 packages meeting all 9 record checks, by downloads

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
npm · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

Worth knowing before you connect it

  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.4.0, published 2026-11-10 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-06 to 2026-11-10; 3 in the 90 days before the 2026-11-12 snapshot.
Most recent 3 versions
  • 0.4.0 · 2026-11-10
  • 0.3.1 · 2026-11-06
  • 0.1.1 · 2026-11-06
(versions still listed in the registry only)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-14

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.3.1 (published 2026-11-06) → 0.4.0 (published 2026-11-10), between the registry lists of 2026-11-09 and 2026-11-12.

The publisher’s GitHub release note for v0.4.0 (“SIGSHIP 0.4.0”), published 2026-11-10.

Read the release note (the publisher’s text, shown as plain text)
### Added
- MCP 0.4: `path` is optional and defaults to the folder the server was started in. `sigship_check` returns structured content with a schema: the verdict, counts, accepted risks, findings grouped by check with up to 10 places each and a count of the rest, `since` (fixed, left, new compared with the last run of the same folder, kept in a small file in the cache folder), and a fix brief worded for the connected client. New tool `sigship_badge` for the badge code after a GO, and the `launch-check` prompt. `sigship_explain` is unchanged. No tool accepts a risk.
- `npx sigship badge <site>`: prints the Self-checked badge code for a site with no account and no network call. With `SIGSHIP_KEY`, registers the site for the Deep self-check badge.
- `npx sigship login` and `npx sigship logout`: sign in to SIGSHIP Cloud with a short code approved in the browser. The token is saved in the cache folder, readable by you only. While signed in, each check reports its verdict, counts, version, date, a repo fingerprint and the folder's name, never code, after the check and without ever failing it. `SIGSHIP_NO_REPORT=1` turns it off.
- A GO in the terminal, Markdown and MCP outputs now ends with `Show it with: npx sigship badge <site>`.
- `--online`: the one free check that uses the network, and only when you ask. It sends the name and version of every package in `package.json` and your lockfile to OSV (`api.osv.dev/v1/querybatch`), nothing else, and reports a package with a known vulnerability as SEV-2. If OSV can't be reached, the scan runs without it and says so.
- Accepted risks: `sigship-accept.json` in the checked folder, a list of `{ rule, file?, reason, expires }`. A matching finding is listed as an accepted risk and does not count for the verdict, which reads `GO with 1 accepted risk` in the terminal, JSON, Markdown, SARIF and HTML outputs. Expired or malformed entries are ignored with a warning. There is no flag or command that accepts a risk.
- `--sarif`: SARIF 2.1.0 output with one rule per check and a stable fingerprint per result, for GitHub code scanning.
- `--tool lovable|cursor|bolt|claude|replit|windsurf`: words the fix prompt for one tool. Without it the prompt is unchanged.
- `npx sigship history [folder]`: finds secrets committed in the past, even ones a later commit removed, with the commit and file and never the value. Reads up to 5,000 commits or 50 MB of `git log -p`.
- `npx sigship init --hook`: a pre-commit hook (`.git/hooks/pre-commit`, or a line in `.husky/pre-commit`) that runs only the secret checks on the staged files and blocks a commit that adds one. `npx sigship hook` is what it runs.
- `init` adds the definition of done to `CLAUDE.md` too, when that file exists.
- `--report --brand "Name" --logo file.png`: the client report with your name and logo instead of SIGSHIP's. The logo is inlined, so the page still loads nothing from the network.
- Pack format v2 for the Pro pack: `projectLacks` (a pattern that must appear somewhere in the project), `policy` checks (`policyFor`, `policyWhere`) that read `create policy` blocks in SQL, and `dep` checks (`depMatch`, `depBelow`) that compare dependency versions against `package.json` and the lockfile. Every v1 field still works.

### Changed
- The checks now run in `src/engine.js`, which takes files already in memory and imports nothing from the file system or the network. `src/scan.js` only loads a folder from disk and calls it. Output is unchanged.
- The scanner reads `yarn.lock` and `pnpm-lock.yaml` for pinned versions.

The release on GitHub

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12; release notes from the GitHub Releases API, checked 2026-11-12.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package sigship

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "sigship": {
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "sigship": {
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "sigship": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"sigship","type":"stdio","command":"npx","args":["-y","sigship@0.4.0","mcp"]}'
Claude Code
claude mcp add --transport stdio sigship -- npx -y sigship@0.4.0 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "sigship": {
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "sigship": {
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.sigship]
command = "npx"
args = ["-y", "sigship@0.4.0", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "sigship": {
      "command": "npx",
      "args": [
        "-y",
        "sigship@0.4.0",
        "mcp"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y sigship@0.4.0 mcp
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.0
Latest stable
0.4.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-14. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-12 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-g2Ht1pv6FYK76CYLQ…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-11-14.

Usage

Downloads
1,716 in the last month

Source: api.npmjs.org · 2026-11-14.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Install-time script (npm). No install-time script in the published package.json (version 0.4.0). Source: registry.npmjs.org/sigship/0.4.0 · read 2026-11-12.
  • Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/sigship/0.4.0 · read 2026-11-12.
  • Node.js version (npm). Needs Node 22 or later (engines.node >=22). Source: registry.npmjs.org/sigship/0.4.0 · read 2026-11-12.
  • MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list @modelcontextprotocol/sdk or any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: registry.npmjs.org/sigship/-/sigship-0.4.0.tgz · read 2026-11-12.
  • Build workflow. Built and published by GitHub Actions workflow .github/workflows/publish-npm.yml in https://github.com/sigship/sigship (npm provenance). Source: read 2026-11-12.

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-12.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.4.0 on npmExists and can be installedmatchesnpm · 2026-11-14
Repository github.com/sigship/sigshipOpens publiclymatchesapi.github.com · 2026-11-14

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.sigship
GitHub owner
an organization (sigship)
Build record
signed and attested
Repository
github.com/sigship/sigship
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-14; security policy read from GitHub · 2026-11-07.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

  • #2,014 of 20,610 packages by monthly downloads, tied with 3 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • #432 of 1,244 packages meeting all 9 record checks, by downloads
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.sigship/sigship

Answered from the data above

Who publishes io.github.sigship/sigship?

The registry ties the namespace io.github.sigship to the GitHub account sigship; only its owner can publish under it. Its linked repository, github.com/sigship/sigship, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.sigship/sigship safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.sigship/sigship been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.sigship/sigship publish a security policy?

Yes: its repository has a public security policy (github.com/sigship/sigship/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.4.0, the latest stable release on npm.

Where is the source code of io.github.sigship/sigship?

In github.com/sigship/sigship, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-12; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-12
Hosting type
registry · 2026-11-12
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · no declaration is not a guarantee
Package registry
registry · 2026-11-12
Freshness
0–30 days
registry updatedAt · 2026-11-12
Lifecycle status
registry · 2026-11-12
License class
package registry · 2026-11-14
Integrity hash
declared (sri)
package registry · 2026-11-14
Signature / provenance
package registry · 2026-11-14
Dependency advisories
none known
npm audit · 2026-11-12
Popularity
1,716 downloads a month
package registry · 2026-11-14
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-11-14
Maintenance
api.github.com · 2026-11-14
Environment
your machine
where it runs, from the hosting type · 2026-11-12

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.sigship/sigship: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/io.github.sigship/sigship

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 9 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.sigship/sigship)](https://protocolprobe.com/mcp/servers/io.github.sigship/sigship)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology