Skip to main content
Glama
Sign In
retained

retained

by arm00pv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to retained

No user-submitted related servers found.

    Related Servers

    • strata

      rx6ru
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read and write a durable, append-only memory with verified provenance, supporting search, record capture, and context preparation across sessions and machines.
      1
      MIT

    • Orenyl

      edison-zhou-nc
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing agent memory with deterministic deletion guarantees, enabling compliant event storage, context retrieval, and audit-proof data management.
      Apache 2.0

    • Ghostkeep

      Akshu24Tech
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.
      -

    • mcp-evidence-ledger

      brianpelow
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server providing an append-only, hash-chained evidence ledger for agent actions, where every record is a tamper-evident receipt cryptographically bound to all prior records and persisted as human-readable JSONL local state. It exposes tools to append records, verify chain integrity (pinpointing tampering), query records by actor/action/target/time, and fetch ledger stats—with no update or delete capabilities by design.
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tool names use distinct memory-related verbs: write, checkpoint, get, search, and verify. Most operations are clearly separable, though write versus checkpoint may be ambiguous without fuller descriptions.

    Naming Consistency5/5

    All five tools follow the same predictable memory_verb snake_case pattern. There are no naming inconsistencies or mixed conventions.

    Tool Count5/5

    Five tools is a well-scoped size for a focused memory server. Each tool appears to cover a distinct part of the memory lifecycle without bloat.

    Completeness3/5

    The surface covers writing, retrieving, searching, checkpointing, and verifying memory. However, there are no obvious delete, update, or list operations, which are notable gaps for a memory-management domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources