io.github.jmeyer1980/neurodivergent-memory
NPM · NEURODIVERGENT-MEMORY
Persistent knowledge graph MCP server for neurodivergent thinking. BM25 search, no cloud LLM.
Available components
Last scanned (5 hours 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 @modelcontextprotocol/sdk 1.28.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jmeyer1980/neurodivergent-memory). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 93 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 823 tokens (~51/item across 16 items; 11 tools + 5 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 1 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.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
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/neurodivergent-memory@0.1.8
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 | jmeyer1980/neurodivergent-memory |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jmeyer1980/neurodivergent-memory/.github/workflows/release.yml@refs/tags/v0.1.8 |
| Rekor log index | 1191833878 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a166bbbc1bd818d3d5b01088875288904e0e741bdae3d45efe5d162b3ca76bf4deece9af6b78997e28745142b340bf4c3e801527cf4f55a172a525b04 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
connect_memories ~57
Create connections between memories (like neural pathways)
| Name | Type | Req | Description |
|---|---|---|---|
| bidirectional | boolean | – | Whether connection goes both ways |
| memory_id_1 | string | yes | First memory ID |
| memory_id_2 | string | yes | Second memory ID |
No output schema declared.
No examples provided.
delete_memory ~33
Permanently delete a memory and remove all its connections
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | ID of the memory to delete |
No output schema declared.
No examples provided.
import_memories ~48
Bulk-import memories from a JSON array. Each entry requires content and district; tags, emotional_valence, and intensity are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | Array of memory entries to import |
No output schema declared.
No examples provided.
list_memories ~68
List stored memories with optional pagination and filters
| Name | Type | Req | Description |
|---|---|---|---|
| archetype | string | – | Optional archetype filter |
| district | string | – | Optional district filter |
| page | number | – | Page number (default 1) |
| page_size | number | – | Results per page (default 20) |
No output schema declared.
No examples provided.
memory_stats ~32
Return aggregate statistics: total count, per-district counts, connection count, most-accessed nodes, and orphan nodes
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
related_to ~62
Find memories related to a given memory ID, ranked by graph proximity + BM25 semantic score
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Source memory ID |
| query | string | – | Optional extra query to bias semantic ranking. If omitted, the source memory content is used. |
No output schema declared.
No examples provided.
retrieve_memory ~29
Retrieve a specific memory by ID
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | ID of the memory to retrieve |
No output schema declared.
No examples provided.
search_memories ~154
Search memories using BM25 semantic ranking. Returns results sorted by relevance score (0-1).
| Name | Type | Req | Description |
|---|---|---|---|
| district | string | – | Optional district filter |
| emotional_valence_max | number | – | Maximum emotional valence filter (-1 to 1) |
| emotional_valence_min | number | – | Minimum emotional valence filter (-1 to 1) |
| intensity_max | number | – | Maximum intensity filter (0-1) |
| intensity_min | number | – | Minimum intensity filter (0-1) |
| min_score | number | – | Minimum relevance score (0-1). Only return results at or above this threshold. |
| query | string | yes | Search query |
| tags | array | – | Optional tag filters (OR logic) |
No output schema declared.
No examples provided.
store_memory ~93
Store a new memory in a specific district of the neurodivergent mind
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The memory content/thought to store |
| district | string | yes | Memory district to store in |
| emotional_valence | number | – | Emotional charge (-1 to 1) |
| intensity | number | – | Mental energy/importance (0-1) |
| tags | array | – | Optional tags for categorization |
No output schema declared.
No examples provided.
traverse_from ~65
Walk the memory graph from a starting node up to N hops deep, returning all reachable memories
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | Maximum hops to traverse (default 2) |
| district | string | – | Optional district filter for results |
| memory_id | string | yes | Starting memory ID |
No output schema declared.
No examples provided.
update_memory ~101
Update an existing memory's content, tags, district, emotional_valence, or intensity
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | New content (optional) |
| district | string | – | New district (optional) |
| emotional_valence | number | – | New emotional charge (optional) |
| intensity | number | – | New intensity (optional) |
| memory_id | string | yes | ID of the memory to update |
| tags | array | – | New tags (optional, replaces existing) |
No output schema declared.
No examples provided.
How do I install the io.github.jmeyer1980/neurodivergent-memory MCP server?
io.github.jmeyer1980/neurodivergent-memory runs locally as an npm package, launched with npx -y neurodivergent-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · neurodivergent-memory
claude mcp add jmeyer1980-neurodivergent-memory -- npx -y neurodivergent-memory
What is the io.github.jmeyer1980/neurodivergent-memory MCP server?
io.github.jmeyer1980/neurodivergent-memory is an MCP server listed in the public MCP registry as io.github.jmeyer1980/neurodivergent-memory. Persistent knowledge graph MCP server for neurodivergent thinking. BM25 search, no cloud LLM. This page covers its npm package (neurodivergent-memory).
Is the io.github.jmeyer1980/neurodivergent-memory MCP server safe to use?
io.github.jmeyer1980/neurodivergent-memory scores 90 out of 100 on VerifyMCP. We recorded 7 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 io.github.jmeyer1980/neurodivergent-memory MCP server expose?
io.github.jmeyer1980/neurodivergent-memory exposes 11 tools: store_memory, retrieve_memory, update_memory, delete_memory, connect_memories, and 6 more. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.
Is the io.github.jmeyer1980/neurodivergent-memory MCP server still maintained?
io.github.jmeyer1980/neurodivergent-memory 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 io.github.jmeyer1980/neurodivergent-memory MCP server under?
io.github.jmeyer1980/neurodivergent-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.