Skills/npm/mcp-structured-memory

mcp-structured-memory@0.2.10

VERIFIED

Publisher claims: "A Model Context Protocol server that automatically maintains structured, domain-specific memory documents for focused projects" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher nmeierpolys · publishing for 477 daysInstalls 1,222Last detonated 1 h ago
$claude mcp add mcp-structured-memory -- npx -y @nmeierpolys/mcp-structured-memory
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.2.9

vet-skills diff mcp-structured-memory 0.2.9 0.2.10

In the sandbox, this version reached for nothing 0.2.9 did not. Compared from the two recorded runs, not from source.

Tool descriptor hashes were not recorded for both runs; renamed or added tools are compared, rewritten descriptions are not.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-21 and scored it 95/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 37 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
17sprocessdependency install exit 0
37sclaimed10 tools: create_memory, add_to_list, get_section, list_memories, get_memory_summary, search_within_memory, update_section, update_list_item, move_list_item, get_full_memory
37stools070e828c014a1feb
37stoolsa7756cce89a31dd5
37stoolsce8c944f0d97733e
37stools0f284c867b3ceda9
37stools0c6b80d8308b09a5
37stoolsc2ab79b2c37f010d
37stoolsca27c3a4de6fb8a0
37stools8dba2e8f6d0d4953
37stools7d979f10fefa2853
37stools3d529a861ff5a5df
37sprocessscript backend runs setup only
37sprocessno install scripts to re-run

Static findings

No findings across 1,770 lines in 36 files.

Cost to the agent

Instructions loaded
≈76 tok
1 file · 36 in bundle
Tool list per prompt
≈1,185 tok
10 tools · 119 per tool
Handshake
497 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 96

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @nmeierpolys/mcp-structured-memory@0.2.10 as of 26 min ago. This is the package itself, not its dependencies.