Skip to main content
Glama
jdbc-mcp-guard

jdbc-mcp-guard

by lyb-java

Related Servers

Alternatives to jdbc-mcp-guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely inspect and mutate relational databases through AST-level SQL guardrails, isolated dry-run rollback previews, automatic PII masking, and virtual schema hiding. Sensitive mutations are gated behind human sign-off via Slack, Microsoft Teams, or a live web approval feed.
      12
      78 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely explore and query databases across SQLite, PostgreSQL, MySQL, and MSSQL, with schema introspection, natural language queries, and data profiling.
      31 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely explore and query SQL databases through read-only, AST-checked SQL, database-enforced read-only transactions, timeouts, row caps, PII masking, and audit logging.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to perform CRUD operations across multiple databases including PostgreSQL, MySQL, and SQL Server using SQLAlchemy. It features configurable permission management and secure connection handling with automatic password redaction.
      4
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely explore and query Microsoft SQL Server databases using read-only SELECT queries, schema discovery, relationship analysis, and configurable security controls.
      1,243 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation3/5

    There are real overlaps: db_schema and db_search_columns both serve introspection, and db_query explicitly claims schema/field/index inspection '一律用它', directly undercutting db_schema. Likewise db_connections and db_dialects both report driver readiness, so an agent may hesitate between them. Descriptions give hints (caching, convenience), but the boundaries are not crisp.

    Naming Consistency4/5

    All tools share a predictable db_ snake_case prefix, which makes the family instantly recognizable. The suffixes mix verb forms (query, execute, search_columns) with plain nouns (connections, dialects, schema), a minor inconsistency but still readable.

    Tool Count5/5

    Six tools is well-scoped for a JDBC guard server: read path, write path, connections, dialects, schema, and column search each earn a slot. Nothing feels padded or missing at the count level.

    Completeness4/5

    Read-only querying, tiered writes, connection listing, dialect/driver readiness, schema introspection and column search cover the core lifecycle of guarded DB access. Gaps are minor: no tool to view the audit log or inspect/verify a single connection, but agents can work around these with db_query or db_connections.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues