io.github.spectra-g/engram
NPM · @SPECTRA-G/ENGRAM-ADAPTER · SCANNED AUG 3
MCP adapter for Engram - organizational memory for AI agents
Available components
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to spectra-g/engram). View diagnostics → Pass
- License check failed: the license (SEE LICENSE IN ../LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 174 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @spectra-g/engram-adapter
claude mcp add spectra-g-engram -- npx -y @spectra-g/engram-adapter
codex mcp add spectra-g-engram -- npx -y @spectra-g/engram-adapter
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"spectra-g-engram": {
"type": "local",
"command": [
"npx",
"-y",
"@spectra-g/engram-adapter"
],
"enabled": true
}
}
} openclaw mcp add spectra-g-engram --command npx --arg -y --arg @spectra-g/engram-adapter
mcp_servers:
spectra-g-engram:
command: "npx"
args: ["-y", "@spectra-g/engram-adapter"] {
"mcpServers": {
"spectra-g-engram": {
"command": "npx",
"args": [
"-y",
"@spectra-g/engram-adapter"
]
}
}
} 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 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +13
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 +40
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: spectra-g/engram security
- License: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: SEE LICENSE IN ../LICENSE functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +20
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 27 Jul 26 26
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@spectra-g/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- 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:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:bba86120e835c9cd6b60ee846958b775fc05725bc42d475a8114f84e72632eb793461d94f36d9b6916382c8b224e2858a1b64d97c740dd269fcd86742
- Discovery method:
- attestation_endpoint
Dependencies 99 packages
99 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.