Connect EchelonGraph CVE & Exposure and your agent gets 16 tools, among them check_affected, check_sbom, cve_exposure. It answers at https://mcp.echelongraph.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 3 October 2026; the last check, on 18 November 2026, succeeded.
CVEs (NVD, CISA-KEV, EPSS, GHSA) and per-CVE exposure from Shodan data (© Shodan). Free, keyless.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_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 whose Inputs: product, ecosystem, package, version, full |
check_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 wi Inputs: purls, sbom, full |
cve_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 version Inputs: cve_id, full |
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_p Inputs: cve_id, full |
cve_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 Inputs: cve_id, ecosystem, package, version, full |
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 mo Inputs: full |
epss_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, nul Inputs: cve_id, full |
exposure_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, unauthenticate Inputs: full |
get_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_due Inputs: cve_id, full |
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 or Inputs: cwe_id, page, full |
get_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), affect Inputs: vendor, advisory_id, full |
kev_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), kev Inputs: since, until, ransomware, vendor, limit, cursor |
scan_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), Inputs: files, full |
search_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 c Inputs: search, severity, min_cvss, sort, limit, offset |
search_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 Inputs: query, vendor, severity, has_cve, limit, offset |
vendor_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 Al Inputs: cve_id, full |
Every block below points at https://mcp.echelongraph.io/mcp. Pick your client and copy.
claude mcp add --transport http echelongraph-cve-exposure https://mcp.echelongraph.io/mcp
{
"mcpServers": {
"echelongraph-cve-exposure": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.echelongraph.io/mcp"]
}
}
}{
"mcpServers": {
"echelongraph-cve-exposure": {
"url": "https://mcp.echelongraph.io/mcp"
}
}
}{
"servers": {
"echelongraph-cve-exposure": {
"type": "http",
"url": "https://mcp.echelongraph.io/mcp"
}
}
}{
"context_servers": {
"echelongraph-cve-exposure": {
"url": "https://mcp.echelongraph.io/mcp"
}
}
}{
"mcpServers": {
"echelongraph-cve-exposure": {
"serverUrl": "https://mcp.echelongraph.io/mcp"
}
}
}{
"mcpServers": {
"echelongraph-cve-exposure": {
"url": "https://mcp.echelongraph.io/mcp"
}
}
}name: EchelonGraph CVE & Exposure
version: 0.0.1
schema: v1
mcpServers:
- name: EchelonGraph CVE & Exposure
type: streamable-http
url: https://mcp.echelongraph.io/mcp{
"mcpServers": {
"echelongraph-cve-exposure": {
"httpUrl": "https://mcp.echelongraph.io/mcp"
}
}
}{
"mcpServers": {
"echelongraph-cve-exposure": {
"type": "http",
"url": "https://mcp.echelongraph.io/mcp"
}
}
}{
"mcpServers": {
"echelongraph-cve-exposure": {
"url": "https://mcp.echelongraph.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.echelongraph.io%2Fmcp&type=streamable_http&id=echelongraph-cve-exposure&name=EchelonGraph%20CVE%20%26%20Exposure
It answered our last check on 18 November 2026 in 208 ms. Over 4 checks since 3 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by echelongraph.io and served from mcp.echelongraph.io, the vendor's own domain: https://mcp.echelongraph.io/mcp.
16, as returned by the server's own tools/list on 20 November 2026: check_affected, check_sbom, cve_exposure, cve_intel, cve_remediation, cve_summary, epss_history, exposure_radar, and 8 more.
It answered our last check on 18 November 2026 in 208 ms. Over 4 checks since 3 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.echelongraph.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.echelongraph. Endpoint host: mcp.echelongraph.io. ARD identifier: urn:air:io.echelongraph:mcp:echelongraph-mcp.
First indexed 3 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.