sources — EchelonGraph CVE & Exposure MCP Resource
sources
is one of 2 resources on the
EchelonGraph CVE & Exposure
MCP server. Connect the server and your client can attach it as context.
by client
How to attach sources from your client
- Claude Code EchelonGraph CVE & Exposure Resource/sources run in your project directory
- Claude Desktop EchelonGraph CVE & Exposure Resource/sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EchelonGraph CVE & Exposure Resource/sources ~/.cursor/mcp.json
- VS Code EchelonGraph CVE & Exposure Resource/sources .vscode/mcp.json
- Zed EchelonGraph CVE & Exposure Resource/sources ~/.config/zed/settings.json
- Windsurf EchelonGraph CVE & Exposure Resource/sources ~/.codeium/windsurf/mcp_config.json
- Cline EchelonGraph CVE & Exposure Resource/sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EchelonGraph CVE & Exposure Resource/sources ~/.gemini/settings.json
- Grok EchelonGraph CVE & Exposure Resource/sources .mcp.json (in your project root)
- ChatGPT EchelonGraph CVE & Exposure Resource/sources Settings → Connectors → Advanced → Developer mode
- Claude.ai EchelonGraph CVE & Exposure Resource/sources Settings → Connectors → Add custom connector
- LangChain EchelonGraph CVE & Exposure Resource/sources pip install langchain-mcp-adapters
Other resources on this server
EchelonGraph CVE & Exposure also offers 4 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 4 October 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.