Skip to main content
Glama

Related Servers

Alternatives to Sentinel Memory MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • F
      license
      D
      quality
      B
      maintenance
      Provides 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.
      77
      6
      -
    • A
      license
      A
      quality
      B
      maintenance
      A local-first MCP server for retrieving a small evidence set and recording reviewed conclusions, policy-gated and redacted without giving an agent general filesystem access.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that indexes Markdown, Word, HTML, and PDF documents into a SQLite knowledge graph with CJK+Latin full-text search and cross-document reference tracking. Runs drift audits to surface stale policies, conflicting research claims, superseded ADRs, and undocumented code exports.
      10
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local static-analysis assistant for Android malware research that manages investigation cases, exposes MCP tools via a local server, and persists evidence-backed findings without cloud dependency.
      MIT

    TDQS

    B3/5.0

    Scored across 20 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues