echelongraph-mcp

MCPattestedlive
v2.7.1io.echelongraphMITUpdated 4d agonpmGitHub

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

Endpoint healthlive
checked 10h ago · 401ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
3kDownloads/wk
2GitHub stars
1Forks
4d agoLast update
Package
Authorio.echelongraph
LicenseMIT
Version2.7.1
Sourcenpm+mcp-registry
npmechelongraph-mcp
GitHubechelongraph/echelongraph-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 313af8a
Dependencies✓ 3 resolved · none vulnerable
Tool surface11 tools · none privileged
Security scan✓ Cleanv2.7.1 · todayHow well does this scan work?
EvalsNone
IndexedOct 9, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

11 tools · none privileged
Statically extracted from the published packagev2.7.1 · 4h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

cve_intelNo description published

This tool published no description. Forge does not invent one.

get_cweNo description published

This tool published no description. Forge does not invent one.

cve_summaryNo description published

This tool published no description. Forge does not invent one.

search_cvesNo description published

This tool published no description. Forge does not invent one.

get_cveNo description published

This tool published no description. Forge does not invent one.

cve_exposureNo description published

This tool published no description. Forge does not invent one.

exposure_radarNo description published

This tool published no description. Forge does not invent one.

kev_recentNo description published

This tool published no description. Forge does not invent one.

vendor_advisories_for_cveNo description published

This tool published no description. Forge does not invent one.

get_vendor_advisoryNo description published

This tool published no description. Forge does not invent one.

search_vendor_advisoriesNo description published

This tool published no description. Forge does not invent one.

0 of 11 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

11 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-10 — observed resolution, not a publisher declaration.

3 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Topics

Related in security