How to Use CVE.org recent CVE changes in Manus
Find CVE records newly published or updated during a recent period. Use it to discover records for review and catch revisions to vulnerabilities already on your watchlist.
Prompts to try with CVE.org recent CVE changes in Manus
Copy an example into Manus, or ask in your own words.
Use CVE.org recent CVE changes to summarize newly published CVEs from the past 24 hours. Give me the returned identifiers for follow-up research.
Use CVE.org recent CVE changes to list updated CVEs from the past 48 hours. Keep them separate from newly published records.
Use CVE.org recent CVE changes to look this up and give me the result as a table.
Pull the latest numbers from CVE.org recent CVE changes and tell me what changed since last week.
Check CVE.org recent CVE changes and summarize what you find in three bullet points.
How to set up CVE.org recent CVE changes in Manus
Pick the way that suits you. Each takes about two minutes.
Use the Manus connector
- Add a custom MCP connector
In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.
Use the Spiral skill
- Send Manus this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run CVE.org recent CVE changes
One request; the result comes back by polling or a webhook.
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/recent_changes", "input": { "to": "<to>" } }'
Then paste one of the prompts above: Manus finds CVE.org recent CVE changes on Spiral, shows the price and runs it.
CVE.org recent CVE changes providers and prices
Spiral runs CVE.org recent CVE changes through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Manus for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Hours | 1 to 168 | Window ending now, in hours. Default 24. Mutually exclusive with from/to. | |
| Limit | 1 to 500 | Rows per page, default 100. | |
| Change | all, new, or updated | all (default), new (newly published) or updated. |
Every API field of CVE Program (CVE.org) CVE Services · Recent changes is on its tool page: open its card above.
What can you do with CVE.org recent CVE changes in Manus?
Turn a CVE identifier or reporting question into a short evidence brief. A chat agent can explain affected products, summarize public references, and identify the CNA responsible for a product's scope.
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.
More on CVE.org recent CVE changes and Manus
Overview
CVE.org recent CVE changes in other agents
Questions about CVE.org recent CVE changes in Manus
Can Manus use CVE.org recent CVE changes?
Yes. Add Spiral to Manus as an MCP server, and Manus can find and run CVE.org recent CVE changes like any built-in tool.
How much does CVE.org recent CVE changes cost in Manus?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.
Do I need an Alexandria account to use CVE.org recent CVE changes in Manus?
No. Spiral runs CVE.org recent CVE changes 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 recent CVE changes in Manus?
About two minutes: add a custom MCP connector, then sign in to Spiral and approve.
Does Manus wait while CVE.org recent CVE changes runs?
CVE.org recent CVE changes runs in the background. Manus 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.
Start using CVE.org recent CVE changes in Manus
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Manus:
set up https://spiral.ai/SKILL.md


