io.github.spectra-g/engram
NPM · @SPECTRA-G/ENGRAM-ADAPTER
MCP adapter for Engram - organizational memory for AI agents
Available components
Last scanned (17 hours ago)
Scores higher than 91% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency57
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to spectra-g/engram). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 267 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 411 tokens (~102/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 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.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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/@spectra-g/engram-adapter@0.2.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | spectra-g/engram |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/spectra-g/engram/.github/workflows/release.yml@refs/tags/v0.2.11 |
| Rekor log index | 936968628 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bba86120e835c9cd6b60ee846958b775fc05725bc42d475a8114f84e72632eb793461d94f36d9b6916382c8b224e2858a1b64d97c740dd269fcd86742 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 30 |
| 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 →
get_impact_analysis ~103
Analyzes the blast radius and coupling of files to prevent breaking changes. This tool reveals which other files are frequently co-committed with the target file, helping you understand what else might be affected by your changes. Use cases: bug fixes, feature additions, refactoring, code review.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Path to the file to analyze, relative to repo root |
| repo_root | string | yes | Absolute path to the git repository root |
No output schema declared.
No examples provided.
get_usage_metrics ~63
Get usage statistics for this repository including how many analyses have been performed, risk distributions, notes created, and performance metrics. Useful for understanding your usage patterns and the health of the codebase analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_root | string | yes | Absolute path to the git repository root |
No output schema declared.
No examples provided.
read_project_notes ~120
Read project notes (memories) about files before working on them. Use this when starting work on a file or investigating an area of the codebase to see if there are important notes, learnings, or context that have been saved. Can search by query text, filter by file path, or list all notes.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Filter notes for a specific file path |
| query | string | – | Search query to match against note content and file paths |
| repo_root | string | yes | Absolute path to the git repository root |
No output schema declared.
No examples provided.
save_project_note ~125
Save important context, decisions, or learnings about a file or symbol for future reference. Use this when you discover important information about code behavior, architectural decisions, bug fixes, or gotchas that would be valuable for future work. Notes are stored persistently and will appear in future impact analysis results.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | File path the note relates to |
| note | string | yes | The note content to save |
| repo_root | string | yes | Absolute path to the git repository root |
| symbol_name | string | – | Optional symbol name the note relates to |
No output schema declared.
No examples provided.
How do I install the io.github.spectra-g/engram MCP server?
io.github.spectra-g/engram runs locally as an npm package, launched with npx -y @spectra-g/engram-adapter. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @spectra-g/engram-adapter
claude mcp add spectra-g-engram -- npx -y @spectra-g/engram-adapter
What is the io.github.spectra-g/engram MCP server?
io.github.spectra-g/engram is an MCP server listed in the public MCP registry as io.github.spectra-g/engram. MCP adapter for Engram - organizational memory for AI agents. This page covers its npm package (@spectra-g/engram-adapter).
Is the io.github.spectra-g/engram MCP server safe to use?
io.github.spectra-g/engram scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.spectra-g/engram MCP server expose?
io.github.spectra-g/engram exposes 4 tools: get_impact_analysis, save_project_note, read_project_notes, get_usage_metrics. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Is the io.github.spectra-g/engram MCP server still maintained?
io.github.spectra-g/engram 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.