GhostFree

What GhostFree MCP server does

The GhostFree MCP server examines dependency manifests in a repository and turns the discovered package versions into vulnerability findings. It supports manifests such as package.json, requirements.txt, go.mod, Cargo.toml, pom.xml, and .csproj files. Results are grouped by ecosystem and can be limited to a minimum severity of CRITICAL, HIGH, MEDIUM, or LOW.

GhostFree uses OSV.dev for the initial CVE lookup. For findings selected for investigation, it can retrieve CVSS details, CWE classifications, reference links, and CISA Known Exploited Vulnerabilities status through NVD and KEV data. This makes it useful for separating urgent findings from issues that need additional context.

How it works

The recommended workflow starts with /ghostfree.scan in the connected coding assistant. GhostFree first discovers manifests and packages, then determines the severity threshold. It queries OSV.dev, presents findings in numbered groups of up to 10, and lets you choose which entries to inspect further.

An enriched result can include the affected package and version, CVSS information, CWE data, references, exploitation status, and a suggested remediation. Recommendations may include upgrading a direct or transitive dependency, applying a code change, or documenting the issue as an accepted risk. The example workflow also considers whether a dependency is directly imported and whether it appears reachable from application code.

Accepted risks are stored in .ghostfree/accepted.yml. Each record includes a CVE, business reason, expiration date, and severity snapshot. Future scans suppress the CVE until its acceptance expires. The file can be committed so the decision is available to other contributors.

Setup and configuration

GhostFree runs locally through an MCP stdio configuration and can be launched with npx -y ghostfree --repo-path <path>. The repository path may be the current directory or a workspace path. VS Code users can also install the GhostFree extension and start it from the MCP server list.

Create .ghostfree/config.yml in the repository root to set a shared scan threshold:

min_severity: HIGH

The configuration file takes precedence over GHOSTFREE_MIN_SEVERITY. If neither is present, the scan asks for a threshold. GHOSTFREE_DIR changes the directory used for GhostFree state, including accepted.yml and config.yml. NVD_API_KEY is optional and raises the documented NVD rate limit from 5 to 50 requests per 30 seconds.

Tools and capabilities

The GhostFree MCP server exposes six tools:

• discover_dependencies scans manifests and returns pinned packages by ecosystem.
• check_cves queries OSV.dev, applies the severity filter, and accounts for accepted risks.
• enrich_cve obtains NVD CVSS, CWE, references, and CISA KEV status.
• list_accepted_risks shows accepted entries, expiration status, and severity snapshots.
• accept_risk records a CVE decision with a reason, expiry date, and severity snapshot.
• remove_accepted_risk deletes an accepted-risk record using its UUID.

The first four tools are read-only. Accepting or removing a risk changes repository state and requires client confirmation.

Limitations and notes

Accepted-risk severity and CVSS values are snapshots taken when the risk is recorded, rather than live values. Extended expirations may require an explicit confirmation, and accepted-risk records should be reviewed as their expiry dates approach.