@prmichaelsen/remember-mcp
npm
v4.1.0
Published by @prmichaelsen — 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.
Multi-tenant memory system MCP server with vector search and relationships
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 (`esbuild.build.js:2`): 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: port { execSync } from 'child_process'; // Build server (standalone) await esbuild.build({ entryPoints: ['src/server.
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 esbuild.build.js
Each tool and what it can reach — statically extracted from the published source.
remember_admin_inspect_memoryingests untrusted inputremember_confirmreads sensitive dataremember_denyreads sensitive datadotenvno sensitive capabilityremember_admin_collection_statsno sensitive capabilityremember_admin_detect_weaviate_driftno sensitive capabilityremember_admin_get_weaviate_schemano sensitive capabilityremember_admin_healthno sensitive capabilityremember_admin_inspect_user_api_tokensno sensitive capabilityremember_admin_inspect_user_escalation_recordsno sensitive capabilityremember_admin_inspect_user_ghost_configsno sensitive capabilityremember_admin_inspect_user_preferencesno sensitive capabilityremember_admin_list_collectionsno sensitive capabilityremember_admin_search_across_usersno sensitive capabilityremember_create_internal_memoryno sensitive capabilityremember_create_memoryno sensitive capabilityremember_create_relationshipno sensitive capabilityremember_delete_memoryno sensitive capabilityremember_delete_relationshipno sensitive capabilityremember_find_similarno sensitive capabilityremember_get_coreno sensitive capabilityremember_get_preferencesno sensitive capabilityremember_ghost_configno sensitive capabilityremember_moderateno sensitive capabilityremember_publishno sensitive capabilityremember_query_internal_memoryno sensitive capabilityremember_query_memoryno sensitive capabilityremember_query_spaceno sensitive capabilityremember_request_set_trust_levelno sensitive capabilityremember_retractno sensitive capabilityremember_reviseno sensitive capabilityremember_search_byno sensitive capabilityremember_search_internal_memoryno sensitive capabilityremember_search_internal_memory_byno sensitive capabilityremember_search_memoryno sensitive capabilityremember_search_relationshipno sensitive capabilityremember_search_spaceno sensitive capabilityremember_search_space_byno sensitive capabilityremember_set_preferenceno sensitive capabilityremember_update_internal_memoryno sensitive capabilityremember_update_memoryno sensitive capabilityremember_update_relationshipno 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 |
|---|---|---|---|---|
v4.1.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
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 @prmichaelsen/remember-mcp --online
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