Skip to main content
Glama
MCP Variance Log
by truaxki

Related Servers

Alternatives to MCP Variance Log

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Centralizes verbatim local AI conversation history into a SQLite database and exposes it via an MCP server, enabling tools like Claude Code and Codex to retrieve exact context from other tools.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Automatically tracks AI-assisted work sessions, code changes, and commands in Claude Code or Codex CLI, and provides daily stats, weekly reports, and data export through MCP tools.
      23 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables real-time sliding-window token velocity anomaly detection and adaptive rate-limiting through a native STDIO MCP server built entirely on the Python standard library. Exposes deterministic algorithmic checks that report anomalies and throttle behavior as JSON tool results for MCP clients such as Claude Desktop, Cursor, and Antigravity.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Diagnose MCP servers — health checks, tool testing, token cost audits, conflict detection, and security scanning with 50+ prompt injection patterns. Works as CLI or MCP server inside Claude Desktop.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that indexes Claude Code conversation history into SQLite, enabling full-text search across past sessions for context recovery and cross-agent observability.
      10
      3
      MIT

    TDQS

    C2.8/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct purposes (e.g., create_table vs. list_tables), but there is overlap between log-query and read-logs, as both involve logging/retrieving conversation variations, which could cause confusion. Additionally, read_query and write_query are clearly distinct from each other but share the database query domain with other tools like describe_table.

    Naming Consistency2/5

    Naming is inconsistent with mixed conventions: some use snake_case (append_insight, create_table), others use kebab-case (log-query, read-logs), and some are unclear (read_query vs. write_query, which are snake_case but differ in verb style). There is no uniform pattern across all tools, making it harder to predict naming.

    Tool Count4/5

    With 8 tools, the count is reasonable for a server focused on database operations and conversation logging. It covers core functions without being overly bloated, though the scope might feel slightly broad due to mixing database management with logging features.

    Completeness3/5

    For database operations, there is good coverage (create, list, describe, read, write), but lacks update/delete specific tools, relying on write_query for those. For conversation logging, it has logging and retrieval, but no direct management tools like delete_logs or update_logs, leaving minor gaps in the lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues