io.github.GATSV-tech/epiphany
NPM · EPIPHANY-MCP
One private, local memory your AI tools share. Cross-model, on-device, never lose a session.
Available components
Last scanned (22 hours ago)
Scores higher than 66% of npm servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 43 of 161 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 95 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 246 tokens (~123/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/epiphany-mcp@0.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 161 packages
| Packages resolved | 161 |
|---|---|
| Stale | 43 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
recall Recall ~93
Search the user's personal brain by meaning and return the most relevant memories. The brain holds facts about the user AND about their projects, products, plans, and history. Check here FIRST, before web search, for any question that could concern the user's own life or work.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | How many memories to return. Defaults to 5. |
| query | string | yes | What to look up, in natural language. |
No output schema declared.
No examples provided.
remember Remember ~153
Save a thought to the user's personal brain. Capture REASONING, not just a bullet: write what was decided AND why, and the choices behind it, so another model could understand and reason with it later. Then wire it into the graph with `connections`, using memory ids from recall (e.g. this decision `because` #12, this `builds_on` #7). That is what turns memories into thought-strings.
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | – | Explicit reasoning links to existing memories, so recall can reconstruct the chain. |
| content | string | yes | The thought to remember, with its reasoning, as complete standalone sentences. |
| source | string | – | Where this came from (app or context). Optional. |
No output schema declared.
No examples provided.
How do I install the io.github.GATSV-tech/epiphany MCP server?
io.github.GATSV-tech/epiphany runs locally as an npm package, launched with npx -y epiphany-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · epiphany-mcp
claude mcp add gatsv-tech-epiphany -- npx -y epiphany-mcp
What is the io.github.GATSV-tech/epiphany MCP server?
io.github.GATSV-tech/epiphany is an MCP server listed in the public MCP registry as io.github.GATSV-tech/epiphany. One private, local memory your AI tools share. Cross-model, on-device, never lose a session. This page covers its npm package (epiphany-mcp).
Is the io.github.GATSV-tech/epiphany MCP server safe to use?
io.github.GATSV-tech/epiphany scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.GATSV-tech/epiphany MCP server expose?
io.github.GATSV-tech/epiphany exposes 2 tools: remember, recall. Their descriptions and schemas cost roughly 246 tokens of context every time the server is loaded.
Is the io.github.GATSV-tech/epiphany MCP server still maintained?
io.github.GATSV-tech/epiphany is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.GATSV-tech/epiphany MCP server under?
io.github.GATSV-tech/epiphany declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.