Reverie
NPM · @KNOWALL-AI/REVERIE
Graph memory that dreams: Neo4j knowledge-graph memory for AI agents with hybrid search
Available components
Last scanned (1 hour ago)
Scores higher than 93% 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
- 57 of 179 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to knowall-ai/mcp-reverie). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 41 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1022 tokens (~85/item across 12 items; 12 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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_memory" 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 12 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.
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 22 Oct 26 0
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- GHSA-wq5f-xc86-pv6w no longer affects this package ▲ security
- GHSA-rgj7-g3m4-5g8c no longer affects this package ▲ security
- GHSA-f88m-g3jw-g9cj no longer affects this package ▲ security
- 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
- 15 Oct 26 −2
- Stability: pass → 0.80 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 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.
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 Nov 2026 · Analysed npm/@knowall-ai/reverie@0.5.3
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 | knowall-ai/mcp-reverie |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/knowall-ai/mcp-reverie/.github/workflows/release.yml@refs/tags/v0.5.3 |
| Rekor log index | 2946257130 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:048a17fd5270a030185f7d1b5086742880c5507cc8d6f3175735b597a0e785c53cb4a1ed99280177baa2b00c1cb0a35e2d5b0e91d27932bd1c0b2f688 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes | |
| 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 179 packages
| Packages resolved | 179 |
|---|---|
| Deprecated | 1 |
| Stale | 57 |
| 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 →
create_connection ~112
Create a connection between two memories (its good to have connected memories)
| Name | Type | Req | Description |
|---|---|---|---|
| fromMemoryId | number | yes | ID of the source memory |
| properties | object | – | Optional relationship metadata (e.g. {since: "2023-01", role: "Manager", status: "active"}) |
| toMemoryId | number | yes | ID of the target memory |
| type | string | yes | Relationship type such as KNOWS, WORKS_ON, LIVES_IN, HAS_SKILL, PARTICIPATES_IN |
No output schema declared.
No examples provided.
create_memory ~136
Create a new memory in the knowledge graph. Consider that the memory might already exist, so Search → Create → Connect (its important to try and connect memories)
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Memory label: a plain identifier, Capitalised singular by convention (Person, Place, Organization, Project, Event, Topic, Object, Animal, Concept, Meeting, Decision…). Use list_memory_labels first fo… |
| properties | object | yes | Information to store about this memory (use "name" as primary identifier, e.g. {name: "John Smith", age: 30, occupation: "Engineer"}) |
No output schema declared.
No examples provided.
delete_connection ~79
Delete a specific connection between two memories (use with caution - this permanently removes the relationship)
| Name | Type | Req | Description |
|---|---|---|---|
| fromMemoryId | number | yes | ID of the source memory |
| toMemoryId | number | yes | ID of the target memory |
| type | string | yes | Exact relationship type to delete (e.g. WORKS_AT, KNOWS, MANAGES) |
No output schema declared.
No examples provided.
delete_memory ~44
Delete a memory and all its connections (use with caution - this permanently removes the memory and all its connections)
| Name | Type | Req | Description |
|---|---|---|---|
| nodeId | number | yes | ID of the memory to delete |
No output schema declared.
No examples provided.
dream ~44
Deterministically relabel, merge duplicates, and refresh embeddings, with an optional dry run report.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | If true, report planned changes without writing them. |
No output schema declared.
No examples provided.
get_guidance ~45
Get help on using the memory tools effectively
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Topic: connections, labels, relationships, best-practices, examples, or leave empty for all |
No output schema declared.
No examples provided.
list_memory_labels ~50
List all unique memory labels currently in use with their counts (useful for getting an overview of the knowledge graph)
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | Include labels of archived memories (excluded by default). |
No output schema declared.
No examples provided.
memory_stats ~26
Summarize node, relationship, label, embedding, and orphan counts for the graph.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_memories ~55
Run a read-only Cypher query and return up to 200 scrubbed rows.
| Name | Type | Req | Description |
|---|---|---|---|
| cypher | string | yes | Read-only Cypher to execute. |
| params | object | – | Optional parameter map for the Cypher query. |
No output schema declared.
No examples provided.
search_memories ~274
Hybrid keyword + semantic search across the knowledge graph. "Ben Weeks" can also find "Benjamin Weeks" and each result includes _score and _match.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | Relationship depth to include, 0 to 5, defaults to 1 |
| include_archived | boolean | – | Include memories with status "archived" (excluded by default). |
| label | string | – | Filter by memory label |
| limit | integer | – | Maximum results to return, 1 to 200, defaults to 10 |
| order_by | string | – | Sort order such as created_at DESC, name ASC |
| query | string | – | Search text to find in any property. Keyword mode matches any word, while semantic mode can surface close meanings and name variants. |
| search_mode | string | – | Search mode: hybrid (default), keyword-only, semantic-only, or exact (case-insensitive equality on name/aliases/email: use before creating a memory). |
| similarity_threshold | number | – | Semantic similarity threshold, 0 to 1 inclusive, defaults to 0.4. |
| since_date | string | – | ISO date string to filter memories created after this date (e.g., "2024-01-01" or "2024-01-01T00:00:00Z") |
No output schema declared.
No examples provided.
update_connection ~102
Update properties of an existing connection between memories
| Name | Type | Req | Description |
|---|---|---|---|
| fromMemoryId | number | yes | ID of the source memory |
| properties | object | yes | Properties to update/add (e.g. {status: "completed", end_date: "2024-01"}) |
| toMemoryId | number | yes | ID of the target memory |
| type | string | yes | Relationship type to identify which connection to update (e.g. WORKS_AT, KNOWS, MANAGES) |
No output schema declared.
No examples provided.
update_memory ~55
Update properties of an existing memory such as adding more detail or make a change when you find out something new
| Name | Type | Req | Description |
|---|---|---|---|
| nodeId | number | yes | ID of the memory to update |
| properties | object | yes | Properties to update/add |
No output schema declared.
No examples provided.
How do I install the Reverie MCP server?
Reverie runs locally as an npm package, launched with npx -y @knowall-ai/reverie. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @knowall-ai/reverie
claude mcp add ai-knowall-reverie -- npx -y @knowall-ai/reverie
What is the Reverie MCP server?
Reverie is an MCP server listed in the public MCP registry as ai.knowall/reverie. Graph memory that dreams: Neo4j knowledge-graph memory for AI agents with hybrid search. This page covers its npm package (@knowall-ai/reverie).
Is the Reverie MCP server safe to use?
Reverie scores 89 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 5 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 Reverie MCP server expose?
Reverie exposes 12 tools: search_memories, create_memory, create_connection, update_memory, update_connection, and 7 more. Their descriptions and schemas cost roughly 1,022 tokens of context every time the server is loaded.
Is the Reverie MCP server still maintained?
Reverie is still listed as active in the MCP registry. We last reached this channel on 5 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 Reverie MCP server under?
Reverie declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.