[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [NVD recent vulnerabilities](https://spiral.ai/integrations/muse/nvd-recent-vulnerabilities)

# How to Use NVD recent vulnerabilities in Muse

Fetch NVD records published or modified recently, with available vulnerability assessments. Use it for a security digest or to catch revisions to older CVEs that a new-publications check would miss.

|  |  |
| --- | --- |
| Model | NVD recent vulnerabilities |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with NVD recent vulnerabilities in Muse

- Use NVD recent vulnerabilities for records published during the past seven days. Summarize entries mentioning Google Chrome, with CVE IDs and available severity assessments.
- Use NVD recent vulnerabilities to look this up and give me the result as a table.
- Pull the latest numbers from NVD recent vulnerabilities and tell me what changed since last week.
- Check NVD recent vulnerabilities and summarize what you find in three bullet points.
- Pull the newest data from NVD recent vulnerabilities and give me the result as a table.

## How to set up NVD recent vulnerabilities in Muse

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

### Use the Muse connector

1. **Create an API key**: Create one under API keys in the Spiral console.

2. **Send Muse this message**: Muse reads Spiral's skill and asks for an API key.

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

3. **Give Muse the key**: Paste the key when Muse asks for it, never in the chat itself.

### Use the Spiral skill

1. **Send Muse 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 recent vulnerabilities**: 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/recent",
    "input": {
      "days": 1
    }
  }'
```

Then paste one of the prompts above: Muse finds NVD recent vulnerabilities on Spiral, shows the price and runs it.

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

## NVD recent vulnerabilities tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| days | 1 to 120 | 1 | Window length in days, ending now. |
| change | modified, published | modified | modified lists CVEs whose NVD record changed in the window; published lists newly published CVEs. |
| cursor |  | — | next_cursor from the previous page; pass the same change and filters. Pattern: ^[0-9]{1,8}\.[0-9]{1,15}\.[0-9]{1,15}$. |
| 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}$. |
| page_size | 1 to 50 | 10 | Records per page. |

## What can you do with NVD recent vulnerabilities in Muse?

Create a readable vulnerability brief for software such as Apache HTTP Server or OpenSSL. Explain the available NVD assessments and advisory references, while identifying records whose enrichment is incomplete.

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

### Write a security operations digest

Summarize newly published or changed records for the operations team. Investigate selected CVE IDs and highlight available CISA KEV information alongside severity assessments.

### 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 Muse guides](https://spiral.ai/integrations/muse)

## NVD recent vulnerabilities in other agents

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

## More Muse guides

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

## Questions about NVD recent vulnerabilities in Muse

**Can Muse use NVD recent vulnerabilities?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run NVD recent vulnerabilities like any built-in tool.

**How much does NVD recent vulnerabilities cost in Muse?**

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

**Do I need an Alexandria account to use NVD recent vulnerabilities in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs NVD recent vulnerabilities on its own Alexandria account.

**How long does it take to set up NVD recent vulnerabilities in Muse?**

About two minutes: create an API key, then send Muse this message, then give Muse the key.

**Does Muse wait while NVD recent vulnerabilities runs?**

NVD recent vulnerabilities runs in the background. Muse 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.

