EchelonGraph CVE & Exposure by echelongraph.io

MCP server · indexed, not reviewed

HostedLocalvendor's ownwidely used

Not reviewed

No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.

How the index works

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.
What the official MCP registry says

Facts

MCP registry: io.echelongraph/echelongraph-mcp · 2.6.3
Endpoint: https://mcp.echelongraph.io/mcp
Packages: npm echelongraph-mcp stdio
Source: github.com/echelongraph/echelongraph-mcp
Website: echelongraph.io/pulse/mcp
npm / week: 2.2k
GitHub stars: 0
Registry entry: updated 4 Oct 2026

From the official MCP registry, the package registries and our own checks. JSON · Markdown

Why it's listed

It's published in the registry under echelongraph.io, a namespace the registry only gives to whoever proves they control that domain.
It's in real use: 2,156 npm downloads a week.

Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.