Skip to main content
Glama
dogrucanemek-alt

tugra

by dogrucanemek-alt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tugra

No user-submitted related servers found.

    Related Servers

    • vault

      rhkrohan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to persist and retrieve structured memory across sessions and models via MCP tools for cataloging, searching, and saving facts, with automatic supersession and scope filtering.
      MIT

    • chronomem

      eikarna
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to store, retrieve, and manage bi-temporal, graph-aware facts in an embedded SQLite memory engine with token-budgeted recall and contradiction tracking.
      6
      1
      MIT

    • mnemochain

      Nulfied
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to store and recall an append-only, hash-chained memory with citation-backed semantic search, fact verification, contradiction detection, and replay/audit capabilities through local MCP tools.
      1
      AGPL 3.0

    • Mnemo

      bladeJumper
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to share a portable, user-level memory layer through MCP, allowing them to store, search, update, link, and consolidate facts with optional full-text and vector retrieval.
      7
      9 npm
      MIT

    • AgentBase

      vhspace
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to persistently store and semantically search shared knowledge via MCP tools.
      2
      MIT
    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

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: searching facts, reading by UID, proposing a draft fact, and appending telemetry. There is no meaningful overlap between fact_search, fact_read, fact_propose, and event_report.

    Naming Consistency5/5

    All tool names use lowercase snake_case and an object-first pattern (fact_search, fact_read, fact_propose, event_report). Although event_report lacks the fact_ prefix, it follows the same noun-verb shape, making the naming predictable and consistent.

    Tool Count5/5

    Four tools is a well-scoped surface for a fact-store server: two retrieval paths, one proposal/write path, and one telemetry path. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The search/read/propose set covers the main fact consumption and contribution workflows. Direct lifecycle operations such as update, retire, or approve are absent, but the proposal mechanism and archive flag suggest a curated interface where this is an acceptable minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources