io.github.vnbochkarev-netizen/vibo-memory
NPM · @VIBO-DEV/VIBO-MCP · SCANNED OCT 4
Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory.
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 → 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
- 31 of 92 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 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 154 tokens (~38/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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
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
How do I install the io.github.vnbochkarev-netizen/vibo-memory MCP server?
io.github.vnbochkarev-netizen/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-memory -- npx -y @vibo-dev/vibo-mcp
{
"mcpServers": {
"vnbochkarev-netizen-vibo-memory": {
"command": "npx",
"args": [
"-y",
"@vibo-dev/vibo-mcp"
]
}
}
} {
"servers": {
"vnbochkarev-netizen-vibo-memory": {
"command": "npx",
"args": [
"-y",
"@vibo-dev/vibo-mcp"
]
}
}
} codex mcp add vnbochkarev-netizen-vibo-memory -- npx -y @vibo-dev/vibo-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vnbochkarev-netizen-vibo-memory": {
"type": "local",
"command": [
"npx",
"-y",
"@vibo-dev/vibo-mcp"
],
"enabled": true
}
}
} openclaw mcp add vnbochkarev-netizen-vibo-memory --command npx --arg -y --arg @vibo-dev/vibo-mcp
mcp_servers:
vnbochkarev-netizen-vibo-memory:
command: "npx"
args: ["-y", "@vibo-dev/vibo-mcp"] {
"McpServers": {
"vnbochkarev-netizen-vibo-memory": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@vibo-dev/vibo-mcp"
]
}
}
} assistant mcp add vnbochkarev-netizen-vibo-memory -t stdio -c npx -a -y @vibo-dev/vibo-mcp
{
"mcpServers": {
"vnbochkarev-netizen-vibo-memory": {
"command": "npx",
"args": [
"-y",
"@vibo-dev/vibo-mcp"
]
}
}
} 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 Oct 26 −3
- Stability: pass → 0.80 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 2 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −3
- Stability: pass → 0.80 functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 +1
- 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 5 Oct 2026 · Analysed npm/@vibo-dev/vibo-mcp@0.1.2
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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 ~45
Save a fact to persistent memory. Deduplicated by exact match.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The fact to remember |
| label | string | yes | Short name of the fact |
No output schema declared.
No examples provided.
memory_search ~39
Search persistent memory for relevant facts. Returns facts + token savings.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | What to search for |
No output schema declared.
No examples provided.
memory_usage ~18
Get token savings statistics (today + all-time).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
thread_memory ~52
Thread memory: add message, compress old ones, ask details, get context.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| role | string | – | – |
| text | string | – | – |
| topic | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.vnbochkarev-netizen/vibo-memory MCP server?
io.github.vnbochkarev-netizen/vibo-memory is an MCP server listed in the public MCP registry as io.github.vnbochkarev-netizen/vibo-memory. Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory. This page covers its npm package (@vibo-dev/vibo-mcp).
Is the io.github.vnbochkarev-netizen/vibo-memory MCP server safe to use?
io.github.vnbochkarev-netizen/vibo-memory scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 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.vnbochkarev-netizen/vibo-memory MCP server expose?
io.github.vnbochkarev-netizen/vibo-memory exposes 4 tools: memory_search, memory_add, memory_usage, thread_memory. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.
Is the io.github.vnbochkarev-netizen/vibo-memory MCP server still maintained?
io.github.vnbochkarev-netizen/vibo-memory is still listed as active in the MCP registry. We last reached this channel on 4 October 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.vnbochkarev-netizen/vibo-memory MCP server under?
io.github.vnbochkarev-netizen/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.