Skip to main content
Glama
caiderek

LogCarver MCP

Related Servers

Alternatives to LogCarver MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables safe read-only interaction with SQL Server and Azure SQL databases, providing schema exploration, query linting and analysis, query plan insights, write previews as SELECTs, and a versioned library of .sql queries via MCP.
      29
      15 PyPI
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides read-only SQL Server health and diagnostic tools using DMVs, enabling users to query server health, active queries with blocking, and missing indexes through natural language.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides tools for querying and managing Microsoft SQL Server databases, including stored procedures and SQL Server Agent jobs as code with version control integration.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only access to Turbo HAMLOG amateur radio logs, allowing natural-language search and aggregation of contacts, station history, award progress, and statistics by importing logs from ADIF/CSV or HAMLOG.HDB via the DLL.
      9
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only SQL Server queries across multiple environments with secure keychain credential storage, catalog exploration, and built-in safety guards against destructive operations.
      3
      8 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides secure, read-only access to Microsoft SQL Server with multi-layer protection, enabling safe query execution, schema discovery, and SQL script analysis through natural language.
      2
      -

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool there is no possibility of misselection between tools; its purpose (recovering deleted/changed rows from the SQL Server active transaction log) is stated explicitly and unambiguously.

    Naming Consistency5/5

    The lone name find_deleted_rows follows a clear verb_noun snake_case pattern, which would fit predictably alongside sibling tools. Nothing in the set breaks convention.

    Tool Count2/5

    A server exposing exactly one tool is the 'too few' case for a stated domain; even a narrow forensic capability typically needs helpers (e.g. list log-visible tables, check log space, run an undo script). The single tool is heavy and multi-purpose rather than well-decomposed.

    Completeness3/5

    The core capability is genuinely covered end-to-end for one operation, and limits are honestly documented, but the surface is a dead end: there is no companion tool to apply the suggested undo SQL, no way to list candidate tables/timestamps, and no fallback handling for the refused cases (TRUNCATE/DROP, compressed tables, off-row LOBs).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues