Skip to main content
Glama

Related Servers

Alternatives to Bilinc

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Serves local-first project memory over stdio, exposing tools to inspect project state, search and retrieve context, report memory, and create Git-aware checkpoints for coding agents.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to commit and read shared memory facts that must cite a registered artifact SHA-256 receipt, with confidence that decays over time and a cascade rollback that quarantines a poisoned fact plus every downstream decision derived from it. Exposes provenance tracing (blame), evidence registration, and commit/revert tools over stdio so multi-agent teams can detect and unwind cascading memory poisoning.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a local stdio MCP server that gives AI coding agents a typed, temporal, evidence-backed memory on embedded SQLite, letting them record decisions and constraints, ask why something happened, navigate memory by time, trace proof paths between refs, and export or supersede stored state without rewriting it. It also exposes read-only ChronoLoom view tools so a person and their agent can steer the same multidimensional memory view by semantic intent rather than raw coordinates.
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a clearly stated role, and the descriptions actively disambiguate the risky pairs (commit_mem vs revise, forget vs revise, recall vs list_memories). A few boundaries still blur — recall vs list_memories are both reads over stored memories, and diff vs history both inspect change — but the docs give explicit guidance on when to use which.

    Naming Consistency3/5

    All names are snake_case and readable, but the convention is mixed: some are bare verbs (commit_mem, recall, revise, forget, confirm), some are bare nouns (status, snapshot, history, diff), and one uses a verb_noun form (list_memories). Not chaotic, but no single predictable pattern an agent can rely on.

    Tool Count5/5

    Eleven tools is well within the sweet spot and every one earns its place: write, read, revise, forget, confirm, inspect, checkpoint, restore, and capability discovery. No filler or near-duplicate tools.

    Completeness4/5

    The memory lifecycle is essentially fully covered — create, retrieve, list, revise, confirm, forget/purge, audit history, plus checkpoint/diff/rollback and status discovery. Minor gaps remain: no bulk/batch operations, no tag or source management, and no export path for migrating memories out.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues