LogCarver MCP
Related Servers
Alternatives to LogCarver MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.2915 PyPIMIT
- AlicenseAqualityDmaintenanceProvides 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.31MIT
- AlicenseNot gradedqualityCmaintenanceProvides tools for querying and managing Microsoft SQL Server databases, including stored procedures and SQL Server Agent jobs as code with version control integration.1MIT
- AlicenseAqualityCmaintenanceEnables 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.91MIT
- AlicenseAqualityCmaintenanceEnables read-only SQL Server queries across multiple environments with secure keychain credential storage, catalog exploration, and built-in safety guards against destructive operations.38 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides 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
Scored across 1 tool
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.
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.
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.
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).