Enhx Memory MCP Server

enhx-memory npm v1.0.0

Published by cbuntingde — 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.

Lightweight SQLite-based persistent memory MCP server for AI coding agents. A minimal TypeScript implementation — not as heavy as enhanced-mcp-memory (which uses transformers, embeddings, etc).

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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:

PointsAdoption-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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • get_memoryingests untrusted input
  • add_memoryno sensitive capability
  • add_relationno sensitive capability
  • add_user_messageno sensitive capability
  • bulk_add_memoriesno sensitive capability
  • cleanup_old_datano sensitive capability
  • count_memoriesno sensitive capability
  • create_taskno sensitive capability
  • delete_memoryno sensitive capability
  • delete_taskno sensitive capability
Show 29 more tools ↓
  • detect_and_save_project_conventionsno sensitive capability
  • detect_project_typeno sensitive capability
  • find_duplicatesno sensitive capability
  • get_active_projectno sensitive capability
  • get_auto_ingest_statusno sensitive capability
  • get_database_statsno sensitive capability
  • get_performance_statsno sensitive capability
  • get_project_conventionsno sensitive capability
  • get_project_summaryno sensitive capability
  • get_related_memoriesno sensitive capability
  • get_relationsno sensitive capability
  • health_checkno sensitive capability
  • list_memoriesno sensitive capability
  • list_projectsno sensitive capability
  • list_relation_typesno sensitive capability
  • list_tasksno sensitive capability
  • merge_memoriesno sensitive capability
  • notify_project_changeno sensitive capability
  • optimize_memoriesno sensitive capability
  • recall_memoriesno sensitive capability
  • remember_project_patternno sensitive capability
  • remove_relationno sensitive capability
  • search_memoriesno sensitive capability
  • set_auto_ingestno sensitive capability
  • set_cleanup_policyno sensitive capability
  • set_dedup_policyno sensitive capability
  • start_sessionno sensitive capability
  • update_memoryno sensitive capability
  • update_task_statusno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 0 1.13.0 2026-09-08

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/enhx-memory/badge.svg)](https://mcptrustchecker.com/registry/enhx-memory)
HTML
<a href="https://mcptrustchecker.com/registry/enhx-memory"><img src="https://mcptrustchecker.com/registry/enhx-memory/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/enhx-memory/badge.json via https://img.shields.io/endpoint?url=…

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 enhx-memory --online

Use the free API → How scoring works

More in AI, Memory & Reasoning