[Integrations](https://spiral.ai/integrations) › [VS Code](https://spiral.ai/integrations/vscode) › [NVD vulnerability search](https://spiral.ai/integrations/vscode/nvd-vulnerability-search)

# How to Use NVD vulnerability search in VS Code

Find NVD CVE records for a product, version, or description keyword, with available severity and weakness data. Use it to investigate a software inventory before you have specific CVE IDs.

|  |  |
| --- | --- |
| Model | NVD vulnerability search |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with NVD vulnerability search in VS Code

- Use NVD vulnerability search for Apache Log4j 2.14.1 and compare the returned applicability evidence with this project's dependency inventory. List CVEs requiring review.
- Use NVD vulnerability search for Apache HTTP Server and build a CSV in this project containing returned CVE IDs, descriptions, and available severity assessments. Follow all result pages.
- Use NVD vulnerability search to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from NVD vulnerability search and tell me what changed since last week.
- Check NVD vulnerability search and summarize what you find in three bullet points.

## How to set up NVD vulnerability search in VS Code

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the hosted server**: Use Add to VS Code on the console's Agents & MCP page, or run:

```bash
code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}'
```

2. **Sign in**: VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.

### Use the Spiral skill

1. **Send VS Code this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run NVD vulnerability search**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "nvd-nist-gov/vulnerabilities/search",
    "input": {
      "cursor": "<cursor>"
    }
  }'
```

Then paste one of the prompts above: VS Code finds NVD vulnerability search on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/vscode

## NVD vulnerability search tools and prices

- [NIST National Vulnerability Database (NVD) · Search](https://spiral.ai/tools/alexandria/nvd-nist-gov/vulnerabilities/search) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| cursor |  | — | next_cursor from the previous page. Pattern: ^[0-9]{1,8}$. |
| in_kev |  | — | Only CVEs in CISA's Known Exploited Vulnerabilities catalog. |
| api_key |  | — | Optional NVD API key (raises NVD's limit from 5 to 50 requests per 30 seconds). Sent only in the apiKey header; never placed in URLs or output. Pattern: ^[A-Za-z0-9-]{16,64}$. |
| keyword |  | — | Words that must all appear in the CVE description (NVD keywordSearch). |
| cpe_name |  | — | One full CPE 2.3 name from NVD's CPE dictionary, e.g. cpe:2.3:o:microsoft:windows_10:1607:*:*:*:*:*:*:*. Mutually exclusive with cpe_match. |
| cpe_match |  | — | CPE 2.3 prefix matched against applicability statements, including version ranges: cpe:2.3:a:apache:log4j (all versions) or cpe:2.3:a:apache:log4j:2.14.1 (that version). |

## What can you do with NVD vulnerability search in VS Code?

Turn dependency versions and scanner-reported CVE IDs into a review document backed by NVD evidence. Compare available product applicability, severity assessments, and references with the project's files to identify items that need investigation.

### Prepare a patch review

Find CVEs for deployed products, investigate known IDs, and review recent revisions. Build a review list with descriptions, available severity assessments, affected-product evidence, and advisory references.

### Check dependencies before a release

Compare the application's dependency versions with NVD product applicability data. Look up CVEs already reported by a dependency scanner and identify records that need manual review.

### Maintain vulnerability review evidence

Keep the CVE descriptions, weakness classifications, product applicability evidence, and references used in security reviews. Refresh known records and discover additional records through product searches and recent changes.

### Draft a product advisory brief

Collect NVD evidence for a public software product and turn relevant CVEs into a readable brief. Separate newly published vulnerabilities from changes to previously reported records.

### Revisit a product risk assessment

Search for vulnerabilities associated with a product and review recent records for additional evidence. Flag changed severity, weakness, or affected-product information for reassessment.

### Identify gaps in vulnerability enrichment

Review known CVEs, product search results, and recent records for missing NIST assessments. Separate records awaiting enrichment from records that already contain assessments supplied by other sources.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All VS Code guides](https://spiral.ai/integrations/vscode)

## NVD vulnerability search in other agents

- [Amp](https://spiral.ai/integrations/amp/nvd-vulnerability-search)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/nvd-vulnerability-search)
- [Claude](https://spiral.ai/integrations/claude-desktop/nvd-vulnerability-search)
- [Claude Code](https://spiral.ai/integrations/claude-code/nvd-vulnerability-search)
- [Cline](https://spiral.ai/integrations/cline/nvd-vulnerability-search)
- [Codex](https://spiral.ai/integrations/codex/nvd-vulnerability-search)
- [Cursor](https://spiral.ai/integrations/cursor/nvd-vulnerability-search)
- [Devin](https://spiral.ai/integrations/devin/nvd-vulnerability-search)
- [dots](https://spiral.ai/integrations/dots/nvd-vulnerability-search)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/nvd-vulnerability-search)
- [Gemini](https://spiral.ai/integrations/gemini/nvd-vulnerability-search)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/nvd-vulnerability-search)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/nvd-vulnerability-search)
- [goose](https://spiral.ai/integrations/goose/nvd-vulnerability-search)
- [Grok](https://spiral.ai/integrations/grok/nvd-vulnerability-search)
- [Grok Build](https://spiral.ai/integrations/grok-build/nvd-vulnerability-search)
- [Hermes](https://spiral.ai/integrations/hermes/nvd-vulnerability-search)
- [Instinct](https://spiral.ai/integrations/instinct/nvd-vulnerability-search)
- [Manus](https://spiral.ai/integrations/manus/nvd-vulnerability-search)
- [Muse](https://spiral.ai/integrations/muse/nvd-vulnerability-search)
- [Muse Code](https://spiral.ai/integrations/muse-code/nvd-vulnerability-search)
- [n8n](https://spiral.ai/integrations/n8n/nvd-vulnerability-search)
- [Notion](https://spiral.ai/integrations/notion/nvd-vulnerability-search)
- [OpenClaw](https://spiral.ai/integrations/openclaw/nvd-vulnerability-search)
- [opencode](https://spiral.ai/integrations/opencode/nvd-vulnerability-search)
- [Perplexity](https://spiral.ai/integrations/perplexity/nvd-vulnerability-search)
- [Raycast](https://spiral.ai/integrations/raycast/nvd-vulnerability-search)
- [Windsurf](https://spiral.ai/integrations/windsurf/nvd-vulnerability-search)
- [Zapier](https://spiral.ai/integrations/zapier/nvd-vulnerability-search)

## More VS Code guides

- [NVD recent vulnerabilities](https://spiral.ai/integrations/vscode/nvd-recent-vulnerabilities)
- [Notion API changelog](https://spiral.ai/integrations/vscode/notion-api-changelog)
- [NVD CVE details](https://spiral.ai/integrations/vscode/nvd-cve-details)
- [Notion Docs, Help Center, Pricing, Blog and Templates List releases](https://spiral.ai/integrations/vscode/notion-docs-help-center-pricing-blog-and-templates-list-releases)
- [IBM Cloud pricing records](https://spiral.ai/integrations/vscode/ibm-cloud-pricing-records)
- [Notion blog index](https://spiral.ai/integrations/vscode/notion-blog-index)

## Questions about NVD vulnerability search in VS Code

**Can VS Code use NVD vulnerability search?**

Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run NVD vulnerability search like any built-in tool.

**How much does NVD vulnerability search cost in VS Code?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your VS Code plan is separate.

**Do I need an Alexandria account to use NVD vulnerability search in VS Code?**

No. Spiral runs NVD vulnerability search on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up NVD vulnerability search in VS Code?**

About two minutes: add the hosted server, then sign in.

**Does VS Code wait while NVD vulnerability search runs?**

NVD vulnerability search runs in the background. VS Code starts the run, checks on it and gives you the json when it's ready.

**How quickly does a published CVE appear in NVD?**

NVD says CVEs typically appear within an hour of publication to the CVE List. That is the availability of the record, not a promise that severity and affected-product enrichment will be complete.

**Why can a public advisory mention a CVE that NVD does not contain?**

An advisory can name a CVE before its record is published to the CVE List. NVD does not run the disclosure or CVE publication process, so public mention alone does not mean an NVD record is available.

**Does every NVD record have complete severity and product data?**

No. Since April 15, 2026, NIST has prioritized enrichment for KEV-listed vulnerabilities, software used by the federal government, and critical software; other CVEs remain listed without immediate enrichment.

**Why might a record have a vendor score but no separate NIST score?**

NIST no longer routinely adds its own severity score when the submitting CVE Numbering Authority has already supplied one. A missing NIST assessment therefore does not mean the record has no severity assessment.

**Do older vulnerabilities all have CVSS v3 scores?**

No. NVD says it has no plans to retroactively assess vulnerabilities published before December 20, 2015 with CVSS v3.0 scores.

