Lagaam
OfficialRelated Servers
Alternatives to Lagaam
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Postgres, BigQuery and DuckDB read-only through policy-checked SQL, with AST-based guards that refuse writes and dangerous functions, column masking on the way out, and an audit log of every query. Also exposes schema browsing and query-planning tools so agents can see allowed tables, columns and costs before running anything.MIT
- AlicenseNot gradedqualityCmaintenanceEnforces safety and governance for SQL queries executed by AI agents, providing read-only enforcement, cost estimation, and audit trails.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query governed data warehouses through plain language, returning grounded answers with SQL, confidence grades, and signed receipts while enforcing access, testing, and audit controls.279 PyPI17Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to safely explore and query MySQL, MariaDB, PostgreSQL, SQLite and StarRocks databases through read-only tools for schema listing, table description, schema search, row sampling, query execution, and plan explanation. Enforces least-privilege accounts, engine-level read-only sessions with timeouts, parsed SQL guardrails, and column masking so runaway or unsafe queries are refused.8MIT
- AlicenseBqualityBmaintenanceEnables AI agents to safely describe, query, and compute metrics across SQL databases using open-format semantic models, custom context, and skills, with read-only and dialect-checked execution.11,180 PyPIApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore and query a SQL database safely, answering questions with real data while blocking writes, hiding protected columns, restricting results to one tenant's rows, and logging every call to an audit trail.MIT
TDQS
Scored across 3 tools
The three tools map to clearly distinct stages of a data workflow: discovery (list_catalogs), schema introspection (describe_table), and execution (query_data). There is no overlap in purpose, and the descriptions actively steer the agent between them.
All three names follow the same snake_case verb_noun pattern (list_catalogs, describe_table, query_data). The convention is predictable and self-explanatory.
Three tools is exactly right for a read-only SQL access server — each earns its place with no redundancy. Adding more would only fragment the discover-describe-query workflow.
The surface fully covers the read-only lifecycle: explore, inspect schema, then query. Write operations are absent, but that is a deliberate scope choice rather than a gap, leaving only minor omissions such as metadata or sample-value helpers.