Skip to main content
Glama

Related Servers

Alternatives to Stellar Jay

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Universal verifiable recovery for long-running AI agents with semantic checkpoints, idempotent action ledger and hash chained log as a deny by default MCP server. Framework agnostic with adapters for LangGraph, LangChain and OpenAI plus gateway and OTel.
      24
      Apache 2.0
    • A
      license
      C
      quality
      C
      maintenance
      Free, open-source (MIT), local-first Swiss accounting MCP server: an AI agent posts double-entry journal entries, categorises and chases invoices, and prepares the MWST-Abrechnung (the Swiss VAT return), with a minimalist Studio for human oversight. Posted entries are append-only and immutable, corrections are reversing entries, and every query is tenant-scoped.
      500
      31 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Auditable long-term memory for coding agents: facts carry their evidence and full supersession history, so why explains where a belief came from and forget retires instead of deleting. Runs embedded on a keyless SQLite store (npx -y statecore-mcp) with optional LLM distillation and a self-hosted StateCore server mode.
      6
      52 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with shared communication and persistent state over HTTP and MCP, letting an agent save its progress, search and reuse other agents' prior work, coordinate tasks in shared spaces, exchange direct messages, and hand its role to a successor when a session ends. State is kept on PostgreSQL with signed, append-only records that anyone can verify.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server that lets AI agents query their own LLM call history as a branchable DAG and offload conversation context into immutable, AES-256-GCM-encrypted capsules — restorable in full or per segment, crypto-shreddable, with RAID-style replication. 12 tools, no API keys, no cloud.
      49 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Audit-grade memory backbone for agent teams. Bi-temporal facts (event time + transaction time, with recall(as_of=...) replay), 6-step deterministic retrieval (no LLM in the critical path), conversation ingest with speaker-locked dual-pass extraction, per-tenant Postgres row-level security, and Ed25519-signed provenance. Postgres + pgvector + Neo4j defaults.
      26 PyPI
      14
      MIT

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: status for health, record/correct/retract for the three fact-mutation paths, get_entity for reads, list_changes for auditing, undo_changes for reversal, and save_checkpoint for snapshots. The record/correct/retract trio is cleanly separated by intent (new value vs. replacement vs. no replacement), so there is no realistic misselection risk.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (record_fact, correct_fact, retract_fact, get_entity, list_changes, undo_changes, save_checkpoint). The lone outlier is 'status,' a bare noun, but the deviation is minor and does not impair readability.

    Tool Count5/5

    Eight tools map neatly onto the fact-store lifecycle with no redundant or filler entries. The count is well within the ideal range for a focused append-only fact/audit service.

    Completeness4/5

    The surface covers the full fact lifecycle (record, correct, retract), reading current state, auditing changes, bulk undo, checkpointing, and health. The only soft gap is the absence of a way to list or restore named checkpoints explicitly, which agents can largely work around by re-saving by name.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive