Developer · Local MCP server
EchelonGraph CVE & Exposure
CVEs (NVD, CISA-KEV, EPSS, GHSA) and per-CVE exposure from Shodan data (© Shodan). Free, keyless.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.echelongraph/echelongraph-mcp- Version
- 2.3.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- io.echelongraph
- Namespace
- Namespace verified by the MCP Registry via the domain echelongraph.io · how
- Website
- echelongraph.io/pulse/mcp
- Repository
- github.com/echelongraph/echelongraph-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | echelongraph-mcp | 2.3.4 | stdio |
How to connect EchelonGraph CVE & Exposure
EchelonGraph CVE & Exposure runs locally from a Node.js package published to the npm registry: echelongraph-mcp version 2.3.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y echelongraph-mcp@2.3.4. It reads these environment variables: ECHELONGRAPH_API_BASE and ECHELONGRAPH_API_TIMEOUT_MS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"echelongraph-mcp": {
"command": "npx",
"args": [
"-y",
"echelongraph-mcp@2.3.4"
],
"env": {
"ECHELONGRAPH_API_BASE": "<value>",
"ECHELONGRAPH_API_TIMEOUT_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| EasyBitsPersistent Linux microVMs for agents: root, internet, sub-second resume and a public URL. | Remote & Local · HTTP, stdioLive check: sign-in required |
| EasyEDA CopilotConnect MCP clients to EasyEDA Desktop for schematic and PCB design, routing, inspection, and DRC. | Local · stdio |
| ebmanMCP server for AWS Elastic Beanstalk: read the fleet; --allow-writes adds two-phase writes. | Local · stdio |
| eCFRElectronic Code of Federal Regulations including FAR, DFARS, and agency supplements. 13 tools. | Local · stdio |
| Echo MemoryShared memory for AI agents, as a graph in your own Postgres. Writes never call an LLM. | Remote & Local · HTTP, stdioLive check: sign-in required |
| EchocacheMCP server caching expensive LLM responses: HTTP-style freshness plus semantic recall. | Local · stdio |
| Echorift MCPMCP server for EchoRift infrastructure primitives (BlockWire, CronSynth, Switchboard, Arbiter) | Local · stdio |
| EchoVault MemoryLocal-first memory for coding agents; stores decisions, bugs, and context across sessions. | Local · stdio |