Synaptic Memory MCP Server
synaptic-memory
PyPI
v0.27.0
Published by plateerlab — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Tool "knowledge_unlink" can modify the filesystemMTC-CAP-002
Tool "knowledge_unlink" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool knowledge_unlink
low Mutating tool "knowledge_unlink" declares no destructiveHintMTC-CAP-005
Tool "knowledge_unlink" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool knowledge_unlink
Tools 42
Each tool and what it can reach — statically extracted from the published source.
knowledge_unlinkwrites filesagent_aggregate_nodesno sensitive capabilityagent_compare_searchno sensitive capabilityagent_countno sensitive capabilityagent_deep_searchno sensitive capabilityagent_expandno sensitive capabilityagent_explore_contextno sensitive capabilityagent_filter_nodesno sensitive capabilityagent_find_similarno sensitive capabilityagent_followno sensitive capability
Show 32 more tools ↓
agent_get_documentno sensitive capabilityagent_get_reasoning_chainno sensitive capabilityagent_join_relatedno sensitive capabilityagent_list_categoriesno sensitive capabilityagent_log_actionno sensitive capabilityagent_record_decisionno sensitive capabilityagent_record_outcomeno sensitive capabilityagent_searchno sensitive capabilityagent_search_exactno sensitive capabilityagent_session_infono sensitive capabilityagent_start_sessionno sensitive capabilityagent_top_nodesno sensitive capabilityknowledge_addno sensitive capabilityknowledge_add_chunksno sensitive capabilityknowledge_add_documentno sensitive capabilityknowledge_add_tableno sensitive capabilityknowledge_backfillno sensitive capabilityknowledge_consolidateno sensitive capabilityknowledge_exportno sensitive capabilityknowledge_ingest_pathno sensitive capabilityknowledge_linkno sensitive capabilityknowledge_merge_nodesno sensitive capabilityknowledge_reinforceno sensitive capabilityknowledge_removeno sensitive capabilityknowledge_searchno sensitive capabilityknowledge_snapshotno sensitive capabilityknowledge_statsno sensitive capabilityknowledge_sync_from_databaseno sensitive capabilityknowledge_updateno sensitive capabilityknowledge_update_edgeno sensitive capabilityontology_define_typeno sensitive capabilityontology_query_schemano sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (42 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.27.0 latest |
A 96/100 | 2 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan synaptic-memory --online --registry pypiMore in Data Science & ML
Security scan results for the 2sio MCP server.
Security scan results for the Add MCP server.
Security scan results for the Ai Archive MCP server.
Security scan results for the Aira Semanticscholar MCP server.
Security scan results for the Auseklis MCP server.
Security scan results for the Brewers Almanack MCP server.