ViBo Memory
NPM · @VIBO-DEV/VIBO-MCP
Local-first memory for AI agents: facts with hash-chain provenance, verified recall.
Available components
Last scanned (16 hours ago)
Scores higher than 49% 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
- 30 of 93 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 421 tokens (~52/item across 8 items; 8 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 Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "memory_forget" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.87 functional
- 7 Nov 26 −22
- CVE-2023-54404 affects this package: high ▼ security
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → fail ▼ security
- Schema quality: 46 → 52 ▼ functional
- Tool coverage: 58% → 47% ▼ functional
- Schema quality: good → fair functional
- Destructive annotations: pass → 0 functional
- Package version: 0.2.6 → 0.3.0 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/@vibo-dev/vibo-mcp@0.3.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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
memory_add ~82
Save a durable fact to local memory on this machine. Deduplicated by label+content.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | One self-contained statement |
| label | string | yes | Short stable name, e.g. "client-anna-prefs" |
| level | string | – | L1 normal, L2 sensitive, L3 secret (hidden from search unless asked) |
No output schema declared.
No examples provided.
memory_forget ~41
Delete a fact by exact label or id. Requires confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| target | string | yes | Exact label or fact id |
No output schema declared.
No examples provided.
memory_provenance ~33
Audit local memory: verify the hash chain, show facts with origin and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
memory_search ~55
Search local memory for relevant facts. Use before asking the user to repeat something.
| Name | Type | Req | Description |
|---|---|---|---|
| include_secrets | boolean | – | Include L3 facts |
| limit | number | – | – |
| query | string | yes | What to search for |
No output schema declared.
No examples provided.
memory_usage ~26
Show local memory size and how much context it saves versus pasting facts into the prompt.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_verify ~63
Check factual claims against local memory: CONFIRMED, CONTRADICTS, PARTIAL or NOT FOUND per claim. Use before stating facts about the user, projects, numbers or dates.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | Claims to check |
| mode | string | – | – |
No output schema declared.
No examples provided.
thread_memory ~83
Thread memory: add a message, read recent context, search the thread, or compress older messages into a digest.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| keep | number | – | – |
| query | string | – | What to look for (ask) |
| role | string | – | – |
| text | string | – | Message text (add) |
| topic | string | – | – |
No output schema declared.
No examples provided.
web_search ~38
Not available in this build: page fetching and compression ship in a later release.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ViBo Memory MCP server?
ViBo Memory runs locally as an npm package, launched with npx -y @vibo-dev/vibo-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 · @vibo-dev/vibo-mcp
claude mcp add vnbochkarev-netizen-vibo-mcp -- npx -y @vibo-dev/vibo-mcp
What is the ViBo Memory MCP server?
ViBo Memory is an MCP server listed in the public MCP registry as io.github.vnbochkarev-netizen/vibo-mcp. Local-first memory for AI agents: facts with hash-chain provenance, verified recall. This page covers its npm package (@vibo-dev/vibo-mcp).
Is the ViBo Memory MCP server safe to use?
ViBo Memory scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 ViBo Memory MCP server expose?
ViBo Memory exposes 8 tools: memory_add, memory_search, memory_verify, memory_provenance, memory_forget, and 3 more. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Is the ViBo Memory MCP server still maintained?
ViBo Memory is still listed as active in the MCP registry. We last reached this channel on 21 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 ViBo Memory MCP server under?
ViBo Memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the ViBo Memory MCP server?
VerifyMCP ran 16 checks on ViBo Memory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.