Skip to main content
Glama
thyn-ai

Telys

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Telys

No user-submitted related servers found.

    Related Servers

    • xmemory

      Diadems666
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to store, retrieve, and manage persistent memories locally via an MCP server with hybrid vector and keyword search, plus tools for memory CRUD, search, backup, and import.
      MIT

    • Cortex

      ryanfrigo
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.
      3 npm
      MIT
    • synapse-layer by SynapseLayer

      synapse-layerofficial

      SynapseLayer
      A
      license
      B
      quality
      A
      maintenance
      MCP-native persistent memory for AI agents. Stores and retrieves encrypted memories with Trust Quotient scoring, cross-agent handover protocol, and immutable audit trail. 13 tools. Remote endpoint available.
      13
      13
      Apache 2.0
    • Enigma MCP Server by Enigma-Memory

      Enigma MCP Serverofficial

      Enigma-Memory
      A
      license
      Not graded
      quality
      A
      maintenance
      Offers MCP tools for managing a local AI memory vault, including remembering, searching, context packing, deletion, and verification of receipts.
      38 npm
      1
      Apache 2.0

    • agent-memory

      deuriib
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent memory for AI coding agents, enabling them to save, search (hybrid vector/BM25/concept graph), list sessions, and forget memories via MCP tools.
      3 npm
      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

    A4.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: semantic vs lexical search, insert vs upsert vs update, exact lookup vs similarity search, and list vs count vs stats are clearly differentiated. The overlapping write tools are carefully distinguished by idempotency and target-row semantics.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (search, add, create_collection, list_collections, upsert, update, delete, compact, build_ivf, index_repo). The few noun-style names like ids, count, and stats are conventional and align with their query-like behavior.

    Tool Count4/5

    19 tools is on the higher end but appropriate for a memory server spanning CRUD, two search modes, index maintenance, and repo ingestion. The count is justified by the breadth of the domain, though a leaner set could merge some maintenance tools.

    Completeness4/5

    The tool surface covers the full memory lifecycle: create, add, get, update, upsert, delete, list, count, search, and compaction. Minor gaps exist—notably no tool to drop/delete an entire collection and no way to alter collection-level settings like lexical flag after creation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources