Skip to main content
Glama

Related Servers

Alternatives to Cortex MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents governed, provenance-tagged memory where facts are invalidated rather than deleted and every recall result carries validity dates, confidence, and replacement links. Stores memory in a local SQLite file with tools for remembering, recalling, invalidating, and pinning facts, plus policy enforcement and an audit trail.
      137 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to maintain auditable, local-first long-term memory in a single SQLite file, preserving source evidence and retiring dependent memories when sources are corrected so Claude Code, Cursor, and Codex start from current recorded evidence.
      703 npm
      156
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.
      7
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and their hosts to record actions, tool calls, and human approvals in an append-only, hash-chained log; verify tamper evidence; mask secrets; retrieve recent events; and export audit-ready JSON or CSV on self-hosted infrastructure.
      4
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action and object: creating claims, adding evidence, tracking or updating assumptions, reviewing, retrieving context, and checking health. The boundaries between review and context retrieval, and between creating and updating assumptions, are clear from the descriptions.

    Naming Consistency4/5

    All tools use the same cortex_ prefix and snake_case conventions, with mostly verb_noun names such as create_claim, add_evidence, and get_context. Minor deviations are cortex_health, a noun, and cortex_review, a bare verb.

    Tool Count5/5

    Seven tools is well-scoped for a claim/evidence/assumption review server. Each tool has a clear role without obvious redundancy.

    Completeness4/5

    The surface covers the core workflow of creating claims, attaching evidence, tracking assumptions, reviewing, and retrieving context. Minor gaps exist around updating or deleting claims and evidence, but the append-only audit-style design may make some of these unnecessary.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues