EchoVault Memory
OCI · GHCR.IO/GO-PORTS/ECHOVAULT:0.3.3 · SCANNED AUG 3
Local-first memory for coding agents; stores decisions, bugs, and context across sessions.
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 Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.Unverified
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 104 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1002 tokens (~200/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
oci · ghcr.io/go-ports/echovault:0.3.3
claude mcp add go-ports-echovault -- docker run --rm -i ghcr.io/go-ports/echovault:0.3.3
codex mcp add go-ports-echovault -- docker run --rm -i ghcr.io/go-ports/echovault:0.3.3
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"go-ports-echovault": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/go-ports/echovault:0.3.3"
],
"enabled": true
}
}
} mcp_servers:
go-ports-echovault:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/go-ports/echovault:0.3.3"] {
"mcpServers": {
"go-ports-echovault": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/go-ports/echovault:0.3.3"
]
}
}
} 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.
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +28
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- 26 Jul 26 11
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 oci/ghcr.io/go-ports/echovault:0.3.3
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
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.
memory_context ~83
Get memory context for the current project. You MUST call this at session start to load prior decisions, bugs, and context. Do not skip this step — prior sessions contain decisions and context that directly affect your current task. Use memory_search for specific topics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max memories (default 10) |
| project | string | yes | Project name (required). |
No output schema declared.
No examples provided.
memory_delete ~229
Delete one or more memories to keep your memory store lean and accurate. Use this tool in two ways: 1. Targeted deletion (ids): remove specific memories whose content you have determined is outdated, incorrect, or no longer relevant. Workflow — call memory_context or memory_search to review existing memories, reason about which ones are stale (e.g. a decision was reversed, a bug fix no longer applies, a pattern was removed from the codebase), then pass their IDs here. 2. Bulk deletion by age (older_than_days): remove all memories older than N days, optionally scoped to a project or category. Use this for periodic housekeeping. At least one of `ids` or `older_than_days` must be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Scope bulk deletion to this category (only with older_than_days). |
| ids | array | — | IDs (or prefixes) of memories to delete. |
| older_than_days | number | — | Delete all memories older than this many days. |
| project | string | — | Scope bulk deletion to this project (only with older_than_days). |
No output schema declared.
No examples provided.
memory_replace ~259
Fully replace the content of an existing memory with new, correct information. Prefer this over memory_save when the existing memory contains wrong or outdated information that must be overwritten rather than appended to. memory_save deduplicates and merges; memory_replace discards the old content entirely. Workflow: use memory_search or memory_context to find the memory ID, then call memory_replace with the corrected content. All fields except `id` behave the same as in memory_save.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | decision: chose X over Y. bug: fixed a problem. pattern: reusable gotcha. learning: non-obvious discovery. context: project setup/architecture. |
| details | string | — | Full context for a future agent with zero context. |
| id | string | yes | ID (or prefix) of the memory to replace. |
| impact | string | — | What changed as a result. |
| project | string | — | Project name. |
| related_files | array | — | File paths involved. |
| tags | array | — | Relevant tags. |
| title | string | yes | Short title, max 60 chars. |
| what | string | yes | 1-2 sentences. The essence a future agent needs. |
| why | string | — | Reasoning behind the decision or fix. |
No output schema declared.
No examples provided.
memory_save ~349
Save a memory for future sessions. You MUST call this before ending any session where you made changes, fixed bugs, made decisions, or learned something. This is not optional — failing to save means the next session starts from zero. Save when you: - Made an architectural or design decision (chose X over Y) - Fixed a bug (include root cause and solution) - Discovered a non-obvious pattern or gotcha - Learned something about the codebase not obvious from code - Set up infrastructure, tooling, or configuration - The user corrected you or clarified a requirement Do NOT save: trivial changes (typos, formatting), info obvious from reading the code, or duplicates of existing memories. Write for a future agent with zero context. When filling `details`, prefer this structure: - Context - Options considered - Decision - Tradeoffs - Follow-up
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | decision: chose X over Y. bug: fixed a problem. pattern: reusable gotcha. learning: non-obvious discovery. context: project setup/architecture. |
| details | string | — | Full context for a future agent with zero context. Prefer: Context, Options considered, Decision, Tradeoffs, Follow-up. |
| impact | string | — | What changed as a result. |
| project | string | yes | Project name (required). |
| related_files | array | — | File paths involved. |
| tags | array | — | Relevant tags. |
| title | string | yes | Short title, max 60 chars. |
| what | string | yes | 1-2 sentences. The essence a future agent needs. |
| why | string | — | Reasoning behind the decision or fix. |
No output schema declared.
No examples provided.
memory_search ~82
Search memories using keyword and semantic search. Returns matching memories ranked by relevance. You MUST call this at session start before doing any work, and whenever the user's request relates to a topic that may have prior context.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 5) |
| project | string | — | Filter to project. |
| query | string | yes | Search terms |
No output schema declared.
No examples provided.