LogCarverGuard
Related Servers
Alternatives to LogCarverGuard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceSecure SQL proxy for AI agents. Translates natural language to safe SQL via Claude, validates at the AST level (SELECT-only, no DDL/DML), enforces per-agent row-level security, and audit-logs every query.1MIT

Midplaneofficial
AlicenseNot gradedqualityAmaintenanceSQL guardrails for AI agents, sitting between the agent and Postgres to enforce policies, block destructive queries, and audit all access.5MIT- AlicenseAqualityDmaintenanceExposes any Microsoft SQL Server database to AI agents with multi-database support, keyword lookup, free SELECT queries, and three transport modes (stdio/SSE/Streamable HTTP).41,146 npmMIT

aperion-shieldofficial
FlicenseAqualityAmaintenanceLocal guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.1411-- FlicenseNot gradedqualityDmaintenanceEnables AI agents to inspect schemas, analyze performance, check security, and troubleshoot SQL Server 2019+ databases through a safe, controlled interface.-
- AlicenseNot gradedqualityCmaintenanceEnforces safety and governance for SQL queries executed by AI agents, providing read-only enforcement, cost estimation, and audit trails.Apache 2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single entry point has an unambiguous, well-bounded role: execute SQL under guardrails.
The lone name, execute_sql, follows the standard verb_noun snake_case convention cleanly. There are no other names to conflict with, so consistency is trivially satisfied.
A single tool is thin for a server with this much behavior (read-only mode, batch transactions, blocking rules, auditing). It is defensible as a unified SQL gateway, but the rubric treats 1 tool as borderline.
execute_sql is a complete interface for running and guarding SQL, covering DML, DDL, EXEC and transaction rules. Minor gaps exist: no dedicated tool to inspect the audit log, check current mode, or preview whether a statement would be blocked.