Sentinel Memory MCP
Related Servers
Alternatives to Sentinel Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a locally indexed structural code graph — source entities, callers/callees, Git relationships and recorded mistakes — so they retrieve focused, token-bounded context instead of reading entire files. It runs over local SQLite and can be served through a CLI, agent hooks, an MCP executable and an authenticated local dashboard.66 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides an incident-centric knowledge graph via MCP stdio, enabling storage and query of incidents, systems, signatures, and their causal relationships, with tools for creating, linking, and tracing incidents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables qualitative analysis through a strict TypeDB ontology that verifies evidence quotes and refuses method-breaking changes, while agents use MCP tools to add concepts, themes, dimensions, memos, and checkpoints. Supports append-only event logs for replay, forking, and comparison across staged analysis runs.Apache 2.0
- AlicenseAqualityBmaintenanceEnables an engineering assistant to persist and query local CAD review context—named features, notes, tags, and revision-bound decisions with their requirements and evidence—in SQLite by artifact, entity, text, or tag, marking records stale against a caller-supplied revision. It never opens the CAD file, so it works on a laptop with no CAD software or other server running.5666 npmMIT
- FlicenseDqualityBmaintenanceProvides a local SQLite-backed code context knowledge base with MCP tools for storing and querying code facts, call graphs, semantic info, evidence, and business mappings, plus versioned snapshot publishing and incremental sync.776-
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to store and inspect a persistent local evidence graph of observations, hypotheses and counterfacts, keeping source trails and distinct grounds visible. It tracks revisions across restarts so dependent conclusions are revisited and their support recalculated when a premise changes.MIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action, with clear boundaries between evidence, memory, tasks, scope, and security operations. The security_* cluster is nuanced but differentiated by purpose: skills list requirements, triage evaluates claims, severity computes CVSS, report generates deliverables, and controlled_get performs a bounded request.
All names use lowercase snake_case with a consistent domain prefix, making the set easy to scan. Most follow a noun_verb pattern, but a few are noun_noun (e.g., security_skills, security_severity, memory_context, audit_events), which is a minor deviation.
20 tools is slightly above the typical 3-15 sweet spot, but the domain spans projects, evidence, tasks, security triage, scope control, memory, and audit. Each tool appears to earn its place, so the count is reasonable rather than bloated.
The surface covers core project, evidence, scope, memory, security, finding, and audit workflows. Minor gaps exist, such as no explicit task_create/list or project_list/close, but immutable and versioned designs mitigate them and agents can work around via existing tools.