[Integrations](https://spiral.ai/integrations) › [Google Antigravity](https://spiral.ai/integrations/antigravity) › [CVE.org vulnerability record](https://spiral.ai/integrations/antigravity/cve-org-vulnerability-record)

# How to Use CVE.org vulnerability record in Google Antigravity

Retrieve a known CVE's description, affected products and versions, references, and available enrichment. Use it to investigate one vulnerability and check the evidence behind an alert.

|  |  |
| --- | --- |
| Model | CVE.org vulnerability record |
| 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 CVE.org vulnerability record in Google Antigravity

- Use CVE.org vulnerability record for CVE-2021-44228 and compare its affected products and versions with this repository's Maven dependency files. Write an evidence note with the record's references.
- Use CVE.org vulnerability record for CVE-2021-44228 and check whether our dependency matching code distinguishes log4j-core from other Apache Logging Services projects.
- Use CVE.org vulnerability record to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from CVE.org vulnerability record and tell me what changed since last week.
- Check CVE.org vulnerability record and summarize what you find in three bullet points.

## How to set up CVE.org vulnerability record in Google Antigravity

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

### Use Spiral's MCP server

1. **Open the MCP config**: * Antigravity App: click Customizations, then Installed. In the MCP Servers section, click Copy Config File Path and open that file. * Antigravity IDE: click … at the top of the agent side panel, select MCP Servers, then Manage MCP Servers › View raw config. * Antigravity CLI: edit `~/.gemini/config/mcp_config.json`.

2. **Add the server**: Add Spiral under `mcpServers`:

```json
{
  "mcpServers": {
    "spiral": {
      "serverUrl": "https://api.spiral.ai/mcp"
    }
  }
}
```

3. **Sign in**: In the Antigravity App, open Customizations › Installed. Under MCP Servers, click Authenticate next to Spiral. Sign in to Spiral, pick the organization and click Authorize. Copy the authorization code the browser shows, paste it into Enter authorization code and click Submit. No API key.

### Use the Spiral skill

1. **Send Google Antigravity 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 CVE.org vulnerability record**: 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": "cve-org/vulnerabilities/cve_record",
    "input": {
      "cve_id": "<cve_id>"
    }
  }'
```

Then paste one of the prompts above: Google Antigravity finds CVE.org vulnerability record on Spiral, shows the price and runs it.

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

## CVE.org vulnerability record tools and prices

- [CVE Program (CVE.org) CVE Services · Cve record](https://spiral.ai/tools/alexandria/cve-org/vulnerabilities/cve_record) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | A https://www.cve.org/CVERecord?id=CVE-... URL (or a legacy cve.mitre.org cvename.cgi?name= URL). Mutually exclusive with cve_id. Pattern: ^https?://. |
| cve_id |  | — | CVE id, e.g. CVE-2021-44228 (case-insensitive). Give cve_id or url. Pattern: ^\s*[Cc][Vv][Ee]-[0-9]{4}-[0-9]{4,19}\s*$. |

## What can you do with CVE.org vulnerability record in Google Antigravity?

Build a review queue that connects CVE evidence to the project's dependencies. A coding agent can inspect affected products and versions, identify recent record changes, and resolve assigning organizations.

### Prepare a daily vulnerability brief

Discover newly published and revised CVEs, investigate selected records, and identify the assigning organizations through the CNA directory.

### Review supplier vulnerability evidence

Collect recent CVE changes relevant to Apache or another supplier, inspect affected products and references, and check the assigning CNA's scope.

### Investigate advisory corrections

Use updated CVEs to build a review queue, examine their current records, and locate the CNA's public reporting instructions when a correction needs investigation.

### Audit CVE assignment provenance

Sample recently changed CVEs, read their assignment metadata, and resolve CNA short names into organizations and scopes for an evidence report.

### Review dependencies before a release

Compare affected products and versions in selected CVE records with a project's dependency inventory, using recent changes to find additional records worth checking.

### Revisit existing vulnerability tickets

Match recently updated CVE identifiers against an existing ticket list, then retrieve current records to review affected versions and supporting references.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Google Antigravity guides](https://spiral.ai/integrations/antigravity)

## CVE.org vulnerability record in other agents

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

## More Google Antigravity guides

- [CVE.org recent CVE changes](https://spiral.ai/integrations/antigravity/cve-org-recent-cve-changes)
- [ChatGPT and Codex changelog](https://spiral.ai/integrations/antigravity/chatgpt-and-codex-changelog)
- [CVE.org CNA directory](https://spiral.ai/integrations/antigravity/cve-org-cna-directory)
- [ChatGPT and Codex documentation index](https://spiral.ai/integrations/antigravity/chatgpt-and-codex-documentation-index)
- [CISA KEV vulnerability search](https://spiral.ai/integrations/antigravity/cisa-kev-vulnerability-search)
- [ChatGPT and Codex documentation page](https://spiral.ai/integrations/antigravity/chatgpt-and-codex-documentation-page)

## Questions about CVE.org vulnerability record in Google Antigravity

**Can Google Antigravity use CVE.org vulnerability record?**

Yes. Add Spiral to Google Antigravity as an MCP server, and Google Antigravity can find and run CVE.org vulnerability record like any built-in tool.

**How much does CVE.org vulnerability record cost in Google Antigravity?**

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

**Do I need an Alexandria account to use CVE.org vulnerability record in Google Antigravity?**

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

**How long does it take to set up CVE.org vulnerability record in Google Antigravity?**

About two minutes: open the MCP config, then add the server, then sign in.

**Does Google Antigravity wait while CVE.org vulnerability record runs?**

CVE.org vulnerability record runs in the background. Google Antigravity starts the run, checks on it and gives you the json when it's ready.

**Does CVE include unpublished vulnerability details?**

The CVE Program catalogs publicly disclosed vulnerabilities. An identifier marked RESERVED can exist before its vulnerability details are published.

**How quickly does CVE.org information change?**

The official CVE repository updates about every seven minutes. CNA organization information follows a different schedule: the organization guide says website updates occur on Tuesdays.

**How much recent change history does the source retain?**

The official repository's deltaLog.json normally keeps a rolling 30 days of record modification history. That window describes the change log, not the age of vulnerabilities in the CVE catalog.

**What information identifies an affected vulnerability?**

CVE JSON records include the CVE identifier, affected products and versions, and public references. Those references provide the supporting reports and advisories for further investigation.

**How do I choose the right CNA for a product?**

Choose a CNA whose published scope includes the affected product. CVE.org partner profiles provide reporting instructions, including disclosure policy and contact links.

