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.

GhostFree

NPM · GHOSTFREE

MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.

Available components

0 this week 81 Trust /100

Last scanned (1 hour ago)

Scores higher than 69% of npm servers

Category Security

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 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 499 tokens (~83/item across 6 items; 6 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 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.

  • 4 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 25 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 24 Oct 26 −2
    • CVE-2023-54404 affects this package: high ▼ security
  • 23 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
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/ghostfree@0.2.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 2 findings
ID CVE Severity Vector Fix available
GHSA-gh4j-gqv2-49f6 CVE-2026-41650 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
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 98 packages
Packages resolved 98
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~499 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
accept_risk ~171

Record an accepted risk for a CVE, with a reason and mandatory expiry date. Expiry beyond 1 year requires confirm_extended_expiry=true.

NameTypeReqDescription
confirm_extended_expiryboolean–Set to true to confirm an expiry date more than 1 year away
cve_idstringyesThe CVE ID to accept, e.g. CVE-2021-44228
cvss_scorenumber–CVSS score of the CVE at the time of acceptance (snapshot)
expires_onstringyesExpiry date in YYYY-MM-DD format. Required.
reasonstringyesBusiness justification for accepting this risk
severitystringyesSeverity label of the CVE at the time of acceptance (snapshot). Use UNKNOWN if severity is unavailable.

No output schema declared.

No examples provided.

check_cves ~113

Check a list of packages against OSV.dev for known vulnerabilities. Returns CVEs above the severity threshold as a numbered list, suppressed/accepted risks, expired acceptances, and a count of below-threshold findings.

NameTypeReqDescription
min_severitystring–Minimum severity to surface in detail: CRITICAL, HIGH, MEDIUM, or LOW. If omitted, GhostFree will determine the threshold automatically.
packagesarray–Array of packages to check. If omitted, uses packages from the last discover_dependencies call.

No output schema declared.

No examples provided.

discover_dependencies ~49

Scan the repository for manifest files (requirements.txt, package.json, go.mod, Cargo.toml, pom.xml, *.csproj, Dockerfiles, etc.) and return all pinned dependencies grouped by ecosystem.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enrich_cve ~94

Fetch enrichment data for a specific CVE ID: CVSS vectors and score from NVD, CWE weakness classification, references, and whether it appears in the CISA Known Exploited Vulnerabilities (KEV) catalog. Gracefully degrades if NVD or KEV are unavailable.

NameTypeReqDescription
cve_idstringyesThe CVE ID to enrich, e.g. CVE-2021-44228

No output schema declared.

No examples provided.

list_accepted_risks ~26

List all accepted CVE risks, including whether each acceptance has expired.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_accepted_risk ~46

Remove a previously accepted risk by its UUID acceptance ID.

NameTypeReqDescription
acceptance_idstringyesThe UUID of the accepted risk to remove (from list_accepted_risks)

No output schema declared.

No examples provided.

Install

How do I install the GhostFree MCP server?

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

npm · ghostfree

# add to Claude Code
claude mcp add shane-js-ghostfree -- npx -y ghostfree
Common questions

What is the GhostFree MCP server?

GhostFree is an MCP server listed in the public MCP registry as io.github.shane-js/ghostfree. MCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs. This page covers its npm package (ghostfree).

Is the GhostFree MCP server safe to use?

GhostFree scores 81 out of 100 on VerifyMCP. We recorded 2 known advisories 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 GhostFree MCP server expose?

GhostFree exposes 6 tools: discover_dependencies, check_cves, enrich_cve, list_accepted_risks, accept_risk, remove_accepted_risk. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.

Is the GhostFree MCP server still maintained?

GhostFree 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 GhostFree MCP server under?

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