Local MCP capabilities provider for Expo
Nothing to run from here
Cve Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
CVE intelligence: exploitation (KEV/EPSS), detection coverage, fixed versions, CPE configurations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cve-intelligence-mcp https://cve-security.com/api/mcp
# 2 — ask your agent for something these tools do
# get_cve, search_cves, query_package and 6 more
Cve Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CSAll 1 server
cve-security1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cve-intelligence-mcp https://cve-security.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Full intelligence record for one CVE: per-scorer CVSS, EPSS, CISA KEV/ransomware/SSVC, four remote-detection modalities (the checks that work over the network) plus a host-check tier (self-contained Nuclei templates and Metasploit local modules that run on the system itself) and the Sigma log-detection layer, both kept out of scannable coverage, per-product fixed versions (fixed = first patched bu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | CVE id, such as CVE-2024-3400 |
| configurations_cap | integer | no | How many of NVD's configuration matches products.configurations carries (default 100; 0 to 500). GET /api/cve/{id} carries up to 500. |
Search the catalog. Free text (q) and/or structured filters: vendor (slug), cwe (CWE-nnn), technique (ATT&CK id, such as T1190), year ("2024,2025"), sev ("critical,high"), kev (0|1), kev_from / kev_to (ISO days, half-open CISA listing window; imply kev=1), kev_vendor (the CISA vendorProject string verbatim, such as "Microsoft"), ransomware (0|1), detect (0|1, a detection signal we track), fix (0|1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | — |
| vendor | string | no | — |
| cwe | string | no | — |
| technique | string | no | ATT&CK technique id, such as T1190 or T1059.001 |
| year | string | no | — |
| sev | string | no | — |
| kev | string | no | — |
| kev_from | string | no | ISO day, inclusive lower bound on the CISA listing date |
| kev_to | string | no | ISO day, exclusive upper bound on the CISA listing date |
| kev_vendor | string | no | CISA's vendorProject, verbatim (for example 'Palo Alto Networks') |
| ransomware | string | no | — |
| detect | string | no | — |
| fix | string | no | — |
| automatable | string | no | — |
| epss_gte | number | no | — |
| sighted | string | no | Field sighting window in days: a named sensor network recorded the CVE within the last 7 or 30 days |
| malware | string | no | A published source ties a named malware family, tool, campaign or ransomware group to the CVE |
| watch | string | no | On KEV Watch at tier 1 or 2: reported as exploited by trackers other than CISA, outside CISA KEV |
| chained | string | no | In a known exploit chain: a cited source reports the CVE was used together with another CVE in one exploit chain |
| chainability | string | no | On KCV Watch™: the CVE carries at least one chain candidate at tier A or B, a pair whose extracted exploit capabilities connect or whose records tie the two CVEs together; a candidate is not a confirm |
CVEs affecting one open-source package, by purl (pkg:npm/lodash) or ecosystem + name (Maven names are group:artifact). Returns the CVE list KEV-first with each OSV version range VERBATIM: events plus one render-safe projection: fixed (the upgrade targets) or affected_through (the last VULNERABLE version, so upgrade past it). This tool does not evaluate version membership; compare versions on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purl | string | no | Package URL, such as pkg:npm/lodash or pkg:maven/org.apache.logging.log4j/log4j-core |
| ecosystem | string | no | OSV ecosystem (npm, PyPI, Maven, Go, crates.io, Packagist, RubyGems, NuGet, …) or purl type (pypi, cargo, composer, gem, golang, …) |
| name | string | no | Package name, verbatim (for example @babel/core or org.jenkins-ci.main:jenkins-core) |
The publication change stream: what this site published, stamped with OUR publish time (first_published, kev_added, detection_added, remediation_added, first_sighted, chain_added, and the BOD 26-04 Table 1 input changes ssvc_changed, kev_due_changed, kev_triage_flag_changed, kev_notes_changed, which fire on value changes between snapshots; a timestamp refresh alone fires none). Pass since (YYYY-MM
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | — |
| cursor | string | no | — |
| type | string | no | — |
| cve | string | no | Scope to one CVE's change history, such as CVE-2024-3400 |
| limit | integer | no | — |
The Defender Scoreboard report (CC BY 4.0): exploited vs detectable vs patchable, every figure with its method, caveat and denominator, plus the corpus block and any method-change notes. Cite as "CVE Security Defender Scoreboard, cve-security.com/scoreboard".
No parameter schema on file.
Field sightings: CVEs a named sensor network recorded in the last 7 or 30 days, most sighting days first. A field sighting is a day on which Shadowserver honeypots (cited by VulnCheck KEV and published as daily lists by CIRCL Vulnerability-Lookup) or VulnCheck canary sensors recorded traffic aimed at the CVE. Each row carries first and last sighting day, days sighted in the last 7 and 30, the sens
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | Sighting window in days (default 7) |
| kev | string | no | Restrict to CVEs outside (0) or inside (1) CISA KEV |
| limit | integer | no | 1..500 (default 100) |
Known Chained Vulnerabilities™: pairs of CVEs that a cited source reports were used together in one exploit chain (VulnCheck KEV entry text, Metasploit modules, SigmaHQ rules, press, research or academic sentences, community text judged by a local model). Each row carries both CVEs with their CISA KEV status, the claim kind (observed: the source reports attacks; potential: the source reports they
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | no | Evidence lane: vulncheck_kev, metasploit, sigma, press, research, academic, community, github_poc, exploitdb or exploit_code |
| since | string | no | Pairs first seen on or after this day (YYYY-MM-DD) |
| claim | string | no | observed: the source reports attacks that chained them; potential: the source reports they can be chained |
| limit | integer | no | 1..500 (default 100) |
CVEs whose EPSS exploitation probability rose the most recently. window is "7d" (default) or "30d". Each rise is measured between same-EPSS-model-version scores, so a model release (which shifts the whole distribution) never appears as a mover. A rise raises the priority of a CVE; observed exploitation is recorded through CISA KEV. Returns cve_id, current score, the delta, KEV status and url, larg
| Parameter | Type | Required | Notes |
|---|---|---|---|
| window | string | no | Rise window (default 7d) |
| limit | integer | no | 1..100 (default 25) |
BOD 26-04 Table 1 read for up to 50 CVEs at a stated asset exposure. Per CVE this dataset supplies CISA KEV status and due date, CISA's SSVC Automatable and Technical impact (Vulnrichment) and CISA's forensic triage flag on the KEV entry; you supply exposure for the asset (yes, no, or unknown, which returns both branches). Each item carries the Table 1 row and timeline for the stated exposure, bot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | CVE ids, such as CVE-2024-3400 (1 to 50) |
| exposure | string | no | Whether the asset is publicly exposed, the agency's own per-asset value; unknown returns both branches |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cve Intelligence or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.0.
1.7.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Cve Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.