spatial-memory-mcp
PyPI
v1.11.4
Published by arman-tech — 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.
Spatial bidirectional persistent memory MCP server for LLMs - vector-based semantic memory as a navigable landscape
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — 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.
In the server's implementation (`spatial_memory/core/filesystem.py:92`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: table) result = subprocess.run( ["df", "-T", str(path)], capture_output=True,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server spatial_memory/core/filesystem.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/unit/test_file_security.py:778`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: "/root/.ssh/id_rsa", ], ) @pytest.mark.skipif( os.name == "nt", reason="Unix
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/unit/test_file_security.py
Each tool and what it can reach — statically extracted from the published source.
consolidateno sensitive capabilitycorpus_bridgesno sensitive capabilitydecayno sensitive capabilitydelete_namespaceno sensitive capabilitydiscover_connectionsno sensitive capabilityexport_memoriesno sensitive capabilityextractno sensitive capabilityforgetno sensitive capabilityforget_batchno sensitive capabilityhealthno sensitive capabilityhybrid_recallno sensitive capabilityimport_memoriesno sensitive capabilityjourneyno sensitive capabilitynamespacesno sensitive capabilitynearbyno sensitive capabilityrecallno sensitive capabilityregionsno sensitive capabilityreinforceno sensitive capabilityrememberno sensitive capabilityremember_batchno sensitive capabilityrename_namespaceno sensitive capabilitysetup_hooksno sensitive capabilitystatsno sensitive capabilityvisualizeno sensitive capabilitywanderno sensitive capabilityScan 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 |
|---|---|---|---|---|
v1.11.4 latest |
A 93/100 | 2 | 1.13.0 | 2026-08-25 |
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.
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 spatial-memory-mcp --online --registry pypi
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology