Local MCP capabilities provider for Expo
Nothing to run from here
Vulnerability Exposure 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.
100/100
trust score
16
tools declared
local
runs on your machine
—
downloads a day
What it does
Confirmed vulnerabilities and exposure for IPs, domains and software versions (NVD, CISA KEV, EPSS)
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user vulnerability-exposure-mcp '--' uvx vulnerability-exposure-mcp
# 2 — ask your agent for something these tools do
# investigate_target, resolve_domain, shodan_search and 13 more
Vulnerability Exposure costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MRAll 1 server
MRFrazer251 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. This one runs on your machine: your client starts Vulnerability Exposure as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user vulnerability-exposure-mcp '--' uvx vulnerability-exposure-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SHODAN_API_KEY (Shodan key for service banners (optional: without it the free InternetDB is used)), VIRUSTOTAL_API_KEY (VirusTotal key for IP and domain reputation (optional)), ABUSEIPDB_API_KEY (AbuseIPDB key for IP abuse reports (optional)), NVD_API_KEY (NVD key for a higher rate limit, so version checks run faster (optional)), GREYNOISE_API_KEY (GreyNoise key for more scanner lookups (optional; work-email accounts only)) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
16 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Start here. Classifies the target (public IP, domain or URL, CVE ID, or "software version" such as "nginx 1.20.1") and runs the baseline lookups in code: Shodan, VirusTotal, AbuseIPDB, the registry owner and the keyless threat lists for an IP; DNS, VirusTotal, and the same IP checks for a domain's…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | What to investigate: a public IP ('8.8.8.8'), a domain or URL ('example.com'), a CVE ID ('CVE-2021-44228') or a product and version ('nginx 1.20.1', 'OpenSSH 8.9p1 Ubuntu-3ubuntu0.6'). |
| depth | no | How thorough to be: sets the tool-call budget and how much detail each result keeps. |
Resolve a domain to its public IPv4/IPv6 addresses. Already run for a domain target; use it for other domains you discover.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| investigation_id | no | — |
Shodan host lookup: open ports, services, product versions, hosting org/ASN. Accepts a public IP or a domain (its primary IP is used). Quota-limited: call once per distinct IP. Without SHODAN_API_KEY it falls back to Shodan's free InternetDB: open ports, software, OS and CVEs, but no banners or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | A public IP, or a domain whose primary IP is looked up. |
| investigation_id | no | — |
VirusTotal reputation: how many security engines flag the IP/domain as malicious or suspicious.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | The public IP or domain to check. |
| target_type | string | yes | Whether target is an IP or a domain. |
| investigation_id | no | — |
AbuseIPDB abuse reports and confidence score for a public IP address (not domains).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip_address | yes | — | |
| investigation_id | no | — |
Best tool for software risk. Finds CVEs whose NVD CPE data confirms they affect this exact product version, ranks them by CISA KEV status, EPSS and CVSS, gives each one's patch status and the minimum safe version, and reports CVEs ruled out. Use for every product with a known version (e.g. from…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| software_name | string | yes | The product name, e.g. 'nginx', 'Apache httpd', 'OpenSSH' or 'Next.js'. |
| version | string | no | The exact version, e.g. '1.20.1' or '8.9p1'. Leave it out only when the version is unknown. |
| investigation_id | no | — |
Who a public IP's network is registered to (organisation, range, country, abuse contact), from the regional internet registry over RDAP. Already run for an IP target; use it for other IPs you find. No key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip_address | yes | — | |
| investigation_id | no | — |
Keyless reputation for a public IP: Spamhaus DROP (networks hijacked or run by criminals) and GreyNoise (whether it scans the internet, or is a known business service). Already run for an IP target. GreyNoise allows 10 lookups a day without GREYNOISE_API_KEY.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ip_address | yes | — | |
| investigation_id | no | — |
Hostnames under a domain that have had TLS certificates, from public certificate transparency logs (crt.sh, or Cert Spotter if crt.sh is down). Use it to find other hosts a domain runs; they may no longer exist. No key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| investigation_id | no | — |
Check an Ubuntu or Debian package version against the distro's own security data (via OSV.dev), which counts fixes the distro backports without changing the upstream version. Use it when Shodan lists distro_packages (e.g. OpenSSH_8.9p1 Ubuntu-3ubuntu0.6 gives package 'openssh', package_version…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | The source package name, e.g. 'openssh' or 'nginx'. |
| package_version | string | yes | The installed package version with its distro revision, e.g. '8.9p1-3ubuntu0.6'. |
| distro | string | yes | The distribution. |
| release | string | no | The distro release, e.g. '22.04' or '12'. Found automatically when possible if left out. |
| cve_ids | array | no | CVE IDs to check, usually the version check's affected_cve_ids. |
| investigation_id | no | — |
Full NVD record for one CVE (e.g. 'CVE-2021-44228'): description, CVSS, CWE, affected product ranges, CISA KEV and EPSS. Not needed for CVEs a version check already returned (they carry severity, EPSS, KEV, exploit and fix): use it for a CVE you have no record of, or to read one's full description…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_id | string | yes | One CVE ID, e.g. 'CVE-2021-44228'. |
| investigation_id | no | — |
Check CVE IDs and/or product names against CISA's Known Exploited Vulnerabilities catalog. Product matches only show the product has been exploited before, not that a version is affected. Version checks and CVE lookups already give KEV status for their CVEs: use this once per product for its KEV…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cve_ids | no | — | |
| software_list | array | no | Product names, e.g. ['nginx', 'Exchange Server']. |
| investigation_id | no | — |
Keyword search of NVD returning the most recent matching CVEs (e.g. 'grafana' or 'log4j'). Not version-aware; prefer version_specific_vulnerability_check when a version is known. Search real product or vendor names, at most twice per product (product, then vendor), never fragments of a name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search_term | string | yes | A real product or vendor name, e.g. 'grafana'. |
| investigation_id | no | — |
Facts computed directly from this investigation's tool results, with no model involved, so they are the same on every run: open ports, network, reputation, version check results, upgrade target, and the CISA KEV split into "confirmed for this target" (NVD version match, or the CVE being analysed)…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| investigation_id | yes | — |
Run before giving the final report. Compares your draft with this investigation's tool results and key facts, with no model involved, and lists what they don't support: CVE or advisory IDs no lookup returned, version numbers and EPSS-style percentages that appear nowhere in the data, claims such…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| investigation_id | yes | — | |
| report_markdown | string | yes | Your full draft report, in Markdown. |
Shows which data-source API keys are configured (never their values) and where to get missing ones.
Takes no parameters.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Vulnerability Exposure 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: —
ATrust score 100 / 100
Release 1.0.1 · scanned 29 Oct 2026
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.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digestd06a0292e2f30fdbed9808a6656640872e9e8119f79d9ba085729212458eebf4
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (16 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| investigate_target | no tags | |
| shodan_search | no tags | |
| virustotal_check | no tags | |
| abuseipdb_check | no tags | |
| version_specific_vulnerability_check | no tags | |
| ip_owner | no tags | |
| threat_lists_check | no tags | |
| subdomains | no tags | |
| distro_patch_check | no tags | |
| nvd_lookup | no tags | |
| cisa_kev_check | no tags | |
| cve_search | no tags | |
| get_key_facts | no tags | |
| check_report | no tags | |
| check_api_keys | no tags | |
| resolve_domain | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd06a0292e2f30fdb
Scanned2026-10-29
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.1. Pin a release below and the command asks for exactly that one.
1.0.1
29 Oct 2026
latestNo release note was published with this version.
1.0.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Vulnerability Exposure 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.