Data, search and analytics
echelongraph-mcp
echelongraph-mcp was answering at the last check. Checked on 2026-10-05 (daily check).
CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.
Agents use servers like this to search, query and report on data.
14 read-only0 change data0 high risk
https://mcp.echelongraph.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Status
Newest check: answered with tools, from the daily check, 2026-10-05, 333 ms.
From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-062026-10-05
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Data, search and analytics, ranked by days answering.
Tools
14 tools: 14 read-only, 0 change data, 0 high risk (delete, pay, send or run code).
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 41,313 tokens of tool definitions and a 333 ms handshake.
- read-only
cve_summarySummary 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 modification time among those records. summary.none is not ... - read-only
search_cvesSearch/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 cve_id, severity, cvss_v3_score, echelongraph_score and sc... - read-only
get_cveOne CVE's record: description, severity, cvss_v3_score, cvss_v4_score and cvss_v4_severity (when the record has a CVSS v4 score), echelongraph_score and echelongraph_severity with score_confidence (EchelonGraph's multi-source score) and score_assessed (whether EchelonGraph has scored it), epss_sc... - read-only
cve_exposureInternet-exposure footprint for one CVE from EchelonGraph's KEV-exposure radar: how many internet-facing services (distinct ip:port, returned as exposed_hosts; a machine answering on two ports counts twice) the radar has on record running a version its CVE matcher maps to this CVE, with a country... - read-only
exposure_radarAggregate totals from EchelonGraph's internet-exposure radars, each refreshed on its own schedule: internet-facing services running actively-exploited (CISA-KEV) CVEs, plus the ransomware-linked subset, derived from Shodan data; unauthenticated data stores and observability UIs, found through Sho... - read-only
kev_recentThe 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 row in kev gives cve_id, kev_added_date (CISA's dateAdded), kev_due_date, kev_vendor, kev_product, kev_vuln_name and ... - read-only
epss_historyHow 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 and epss_percentile; current, the record's value now (epss_score, epss_percentile, epss_updated_at); series_kind,... - read-only
check_affectedWhether a product or package at a given version is affected by known CVEs, from the same matcher as echelongraph.io/am-i-affected. Two lookup paths. The CPE path takes product (the NVD CPE product token, such as openssl or nginx) and version, and returns the CVEs whose NVD CPE match criteria name... - read-only
check_sbomCheck a dependency list against EchelonGraph's advisory corpus, one verdict per component. Pass purls (package URLs, up to 2,000 distinct) or sbom (a CycloneDX JSON or SPDX JSON document, as JSON text or as an object, up to 5,000,000 characters). The purls are read from the document by this MCP s... - read-only
cve_intelWeakness, public exploit code, affected packages and fixed versions for one CVE, from EchelonGraph's per-CVE enrichment. Returns cwes (each cwe_id with its name and source), exploits (each with kind, source_name, source_url, first_seen_at and verified_status; at most 10, verified first) with expl... - read-only
get_cweOne 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 CVE.org record classifies under it, rejected and reserved... - read-only
vendor_advisories_for_cveThe vendor-published advisories that name one CVE, newest first, at most 20: for each, vendor, vendor_display_name, vendor_advisory_id, title, severity and cvss_v3_score where the vendor gives them. Covers the vendor feeds EchelonGraph polls, for example Microsoft MSRC, Red Hat, Cisco, Palo Alto ... - read-only
get_vendor_advisoryOne vendor advisory in full, by vendor and the vendor's advisory ID (the vendor and vendor_advisory_id fields of a row from search_vendor_advisories or vendor_advisories_for_cve): title, description, severity, cvss_v3_score, cve_ids and known_cve_ids (those with a record in EchelonGraph's CVE fee... - read-only
search_vendor_advisoriesSearch or list vendor-published 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, vendor_advisory_id, affected_products and cve_ids (search_match substring). A query of 1 or 2 characters match...
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Trust and supply chain
No owner has verified this server yet.
Ships as the npm package echelongraph-mcp, version 2.6.3. No OSV advisory for that version (checked 2026-10-05).
From the checks: The tool list costs more than 10,000 tokens to load; A tool description is over 2,000 characters.
No tool change since tracking began on 2026-10-05.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/mcp.echelongraph.io/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=mcp.echelongraph.io%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/mcp.echelongraph.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/mcp.echelongraph.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=mcp.echelongraph.io%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.