EchelonGraph CVE & Exposure
CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: review pull requests.Similar tools
Listed for the same task: review pull requestsReviews
No review yet. Used EchelonGraph CVE & Exposure? Be the first to help others choose.What it does
EchelonGraph CVE & Exposure is an MCP server, a connector that lets an AI assistant use it as a tool. It can be used hosted (nothing to install) or installed locally.
From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 20h ago (live check)Hosted endpoint
https://mcp.echelongraph.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http echelongraph-cve-exposure https://mcp.echelongraph.io/mcp
Install package
- NPM
echelongraph-mcpv3.2.5 · runs locally (stdio)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"echelongraph-cve-exposure": {
"url": "https://mcp.echelongraph.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 20h agoONLINE EchelonGraph CVE & Exposure answered an MCP connection on 16 Nov 2026 and introduced itself as echelongraph-mcp 3.2.5 (MCP protocol 2025-06-18).
16 tools offered to AI assistants
cve_summary· Summary of EchelonGraph's CVE Pulse feed: summary.total active CVEs, their counts by severity band (summary.critical, summary.high, summary.medium, summary.low), the count with no band (summary.none), and summary.last_updated, the newest mosearch_cves· Search/list CVEs from EchelonGraph's CVE feed (NVD + MITRE-CNA pre-NVD + CISA-KEV + EPSS + GitHub GHSA, each polled on a schedule). Filter by severity, minimum CVSS, free text, and sort; page with limit and offset. Returns cves, each with cget_cve· One CVE's record: description, severity, cvss_v3_score, cvss_v4_score and cvss_v4_severity, echelongraph_score, echelongraph_severity and score_confidence, epss_score and epss_percentile, CISA-KEV status (kev_listed, kev_added_date, kev_duecve_exposure· Internet-exposure footprint for one CVE from EchelonGraph's KEV-exposure radar: how many internet-facing services (distinct ip:port, as exposed_hosts; a machine answering on two ports counts twice) the radar has on record running a versionexposure_radar· Aggregate totals from EchelonGraph's internet-exposure radars: kev_exposure, internet-facing services running actively-exploited (CISA-KEV) CVEs, plus the ransomware-linked subset, derived from Shodan data; exposed_databases, unauthenticatekev_recent· The CVEs CISA has added to its Known Exploited Vulnerabilities (KEV) catalog, newest first, from EchelonGraph's copy of that catalog, which polls CISA's feed every 5 minutes. Each kev row gives cve_id, kev_added_date (CISA's dateAdded), kevepss_history· How one CVE's EPSS score (FIRST's exploit-prediction probability, 0 to 1, with its percentile) has changed, as EchelonGraph recorded it: points, oldest first, each with at, epss_score, epss_percentile and score_date (FIRST's score date, nulcheck_affected· Whether a product or package at a given version is affected by known CVEs, from the same matcher as echelongraph.io/am-i-affected. The CPE path takes product (an NVD CPE product token, such as nginx) and version, and returns the CVEs whosecheck_sbom· Check a dependency list against EchelonGraph's advisory corpus, one verdict per component. For container images and Kubernetes pods, the input is an SBOM of each image, or its purls. Pass purls (package URLs, up to 2,000 distinct, 10,000 wiscan_manifest· Check a project's lockfile or pinned manifest against EchelonGraph's advisory corpus, one verdict per dependency. Pass files: 1 to 20 of filename and content, up to 5,000,000 characters in all. Read: requirements.txt (== and === pins only),cve_intel· Weakness, exploit code, detection checks, affected packages and fixed versions for one CVE, from EchelonGraph's per-CVE enrichment. Returns cwes (each cwe_id with name and source), exploits (each with kind, source_name, source_url, source_pcve_remediation· How one CVE is fixed, as its sources state it, in one answer. Every text is relayed as stated by its source; EchelonGraph has not tested it. An empty list or a remediation_state of none_in_source or not_parsed is not a finding that no fix e
Show 4 more
get_cwe· One CWE (weakness class) and the CVEs classified under it. Returns cwe_id, name and description (from the MITRE CWE catalog EchelonGraph embeds, version catalog_version), total (the active CVEs in EchelonGraph's feed that an NVD, GitHub orvendor_advisories_for_cve· The advisories that name one CVE, newest first, at most 20: for each, vendor, vendor_advisory_id, title, severity and cvss_v3_score where given. Covers the vendor feeds EchelonGraph polls, for example Microsoft MSRC, Red Hat, Cisco, Palo Alget_vendor_advisory· One advisory in full, by vendor and advisory ID (the vendor and vendor_advisory_id of a vendor advisory row, never its advisory_id): title, description, severity, cvss_v3_score, cve_ids and known_cve_ids (in EchelonGraph's CVE feed), affectsearch_vendor_advisories· Search or list advisories, newest first. A query of 3 or more characters is matched case-insensitively as a substring of each advisory's title, description, vendor name, IDs and affected_products (search_match substring). A query of 1 or 2
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Install package | echelongraph-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 3.2.5 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://mcp.echelongraph.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Package registries | npm | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://echelongraph.io/pulse/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/echelongraph/echelongraph-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION15 Nov 20263.2.4 → 3.2.5
- VERSION12 Nov 20263.2.3 → 3.2.4
- VERSION11 Nov 20263.2.2 → 3.2.3
- VERSION11 Nov 20263.2.1 → 3.2.2
- VERSION08 Nov 20263.2.0 → 3.2.1
- VERSION08 Nov 20263.1.5 → 3.2.0
- VERSION07 Nov 20263.1.4 → 3.1.5
- VERSION07 Nov 20263.1.3 → 3.1.4
- VERSION01 Nov 20263.1.2 → 3.1.3
- VERSION25 Oct 20263.1.1 → 3.1.2
- VERSION25 Oct 20263.1.0 → 3.1.1
- VERSION25 Oct 20263.0.2 → 3.1.0
- VERSION17 Oct 20263.0.0 → 3.0.2
- VERSION11 Oct 20262.7.2 → 3.0.0
- VERSION11 Oct 20262.7.1 → 2.7.2
- VERSION06 Oct 20262.7.0 → 2.7.1
- VERSION06 Oct 20262.6.8 → 2.7.0
- VERSION05 Oct 20262.6.7 → 2.6.8
- VERSION05 Oct 20262.6.6 → 2.6.7
- VERSION05 Oct 20262.6.5 → 2.6.6
- VERSION05 Oct 20262.6.3 → 2.6.5
- VERSION04 Oct 20262.6.2 → 2.6.3
- VERSION04 Oct 20262.6.1 → 2.6.2
- VERSION04 Oct 20262.6.0 → 2.6.1
- VERSION04 Oct 20262.5.1 → 2.6.0
- VERSION04 Oct 20262.5.0 → 2.5.1
- CHANGED04 Oct 2026remote access: no → yes
- VERSION04 Oct 20262.3.4 → 2.5.0
- NEW03 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is EchelonGraph CVE & Exposure still online?
Free alerts · no account▲ 0Do you run EchelonGraph CVE & Exposure? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about EchelonGraph CVE & Exposure
How do I connect EchelonGraph CVE & Exposure?
Use the hosted endpoint https://mcp.echelongraph.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does EchelonGraph CVE & Exposure offer?
When Electra Index connected on 16 Nov 2026, it listed 16 tools: cve_summary, search_cves, get_cve, cve_exposure, exposure_radar, kev_recent, epss_history, check_affected and more. The full list is in "Live check" above.
Is EchelonGraph CVE & Exposure online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 20h ago.
What can I use EchelonGraph CVE & Exposure for?
Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities.