Skip to main content
Glama

Related Servers

Alternatives to mcp-database-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first, SQLite-backed document store that lets agents keep notes on a verifiable hash chain and receive signed receipts on recall, so it can flag when previously read information has been superseded or retired. An orient call reports what changed since the agent's last cursor, including a drift banner and retraction list, so stale beliefs surface instead of silently misleading.
      2,065 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware and secret-safe.
      15
      114 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Primary purpose is to maintain a self verifying ledger that requires no consesus. Additional features include support for evm compatible and other block chains.
      6
      12 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Local-first, git-synced memory and system of records for AI agents: a signed append-only event log projected into graph, vector and full-text indexes, with hybrid recall and provenance on every fact.
      64
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server providing a shared, AES-256-GCM encrypted SQLite ledger of structured user state (stack, projects, preferences) that any MCP-aware tool can read/write, with user-held keys and optional zero-knowledge sync.
      1
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: load retrieves, save creates/updates, delete removes, and query searches documents. The descriptions make it easy for an agent to select the right tool for each operation without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., load_json_doc, save_json_doc) with snake_case throughout. The naming is predictable and readable, making it easy to understand each tool's function at a glance.

    Tool Count5/5

    With 4 tools, this server is well-scoped for basic JSON document operations. Each tool earns its place by covering essential CRUD-like functions (load, save, delete, query), which is appropriate for a database server focused on JSON documents.

    Completeness5/5

    The tool set provides complete coverage for the domain of JSON document management: it includes create/update (save), read (load), delete, and query operations. There are no obvious gaps, and agents can perform full lifecycle tasks without dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data