Spiral gives your agent every tool with one account. Browse the tools →

Manus · Developer

How to Use Red Hat CVE search in Manus

Find Red Hat CVE records for a package, product, or advisory, with severity and scoring information. Use it to build a review list before investigating individual vulnerabilities.

Prompts to try with Red Hat CVE search in Manus

Copy an example into Manus, or ask in your own words.

Use Red Hat CVE search to find openssl vulnerabilities affecting Red Hat Enterprise Linux 9. Show their severity, public dates, and available scores.

Red Hat CVE searchManus
Try asking
  • Use Red Hat CVE search to look this up and give me the result as a table.

  • Pull the latest numbers from Red Hat CVE search and tell me what changed since last week.

  • Check Red Hat CVE search and summarize what you find in three bullet points.

  • Pull the newest data from Red Hat CVE search and give me the result as a table.

How to set up Red Hat CVE search in Manus

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

Use the Manus connector

  1. 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
  2. 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

  1. Send Manus 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.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run Red Hat CVE search

    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": "access-redhat-com/vulnerabilities/search",
        "input": {
          "cwe": "<cwe>"
        }
      }'

Then paste one of the prompts above: Manus finds Red Hat CVE search on Spiral, shows the price and runs it.

Red Hat CVE search providers and prices

Spiral runs Red Hat CVE search through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Red Hat Security Data API · Search
access-redhat-com/vulnerabilities/search

Settings you can ask for

Ask Manus for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Severitylow, moderate, important, critical, Low, Moderate, Important, or Critical

Red Hat threat severity.

Page size1 to 10020

Results per page (default 20). Lower it when a page of heavily packaged CVEs exceeds the 1 MiB read limit.

Min cvss3 score0 to 10

Only CVEs whose Red Hat CVSS v3 score is at least this.

Every API field of Red Hat Security Data API · Search is on its tool page: open its card above.

What can you do with Red Hat CVE search in Manus?

Turn Red Hat security records into a product-specific incident or patch brief. A chat app can explain the reported vulnerabilities, product status, and fixing updates in language a maintenance team can use.

Prepare an incident brief

Find relevant package CVEs, inspect their reported product status, and summarize the advisories that deliver fixes for an incident review.

Plan a maintenance window

Build a product-specific vulnerability list and connect the findings to fixing advisories. Group the reported fixes into a maintenance review.

Write remediation tickets

Turn package search results into tickets containing the CVE, Red Hat severity, reported product status, and fixing advisory where available.

Review a security update

Start with an advisory, list the vulnerabilities it addresses, and inspect the CVE assessments to explain the update's security purpose.

Maintain a package watchlist

Repeat searches for packages such as openssl or kernel, compare matching CVEs with the previous review, and investigate newly found records.

Count vulnerabilities and updates separately

Use matching CVEs and their advisory references to produce separate counts of vulnerabilities and fixing updates. Explain where one advisory addresses several CVEs.

Questions about Red Hat CVE search in Manus

Can Manus use Red Hat CVE search?

Yes. Add Spiral to Manus as an MCP server, and Manus can find and run Red Hat CVE search like any built-in tool.

How much does Red Hat CVE search 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 Red Hat CVE search in Manus?

No. Spiral runs Red Hat CVE 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 Red Hat CVE search in Manus?

About two minutes: add a custom MCP connector, then sign in to Spiral and approve.

Does Manus wait while Red Hat CVE search runs?

Red Hat CVE search runs in the background. Manus starts the run, checks on it and gives you the json when it's ready.

Does this cover vulnerabilities from every software vendor?

The scope is Red Hat's product portfolio. Red Hat documents queries for any Red Hat product, including products beyond RHEL.

When does Red Hat publish vulnerability information?

Red Hat says it publishes CVE information and scores immediately after assessing disclosed or coordinated vulnerabilities, unless they are under embargo. It also updates machine-readable security data when fixes are released.

Does a CVE record always include a fixed package version?

No. Red Hat documents fixed package information as optional in a CVE record, including cases where multiple source RPMs share an erratum.

Can one advisory cover several vulnerabilities?

Yes. Red Hat advisories can address multiple CVEs, so counting advisories does not give you the number of vulnerabilities fixed.

Does a product-status review include fixes already released?

Yes, but Red Hat separates unresolved package states from releases that delivered fixes. Both are needed to describe the complete reported status of a CVE across products.

Get started

Start using Red Hat CVE search in Manus

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Manus:

Set up Manus

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options