cost-guard-mcp
Related Servers
Alternatives to cost-guard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnforces safety and governance for SQL queries executed by AI agents, providing read-only enforcement, cost estimation, and audit trails.Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI agents to securely query databases (PostgreSQL, SQLite, MySQL, DuckDB) with read-only defaults and multi-layer SQL injection prevention.81MIT
- 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.11Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables safe, read-only interaction with Google BigQuery through Claude, with layered guardrails preventing dangerous or expensive queries. Exposes tools for listing datasets, tables, estimating costs, and running queries.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query business databases directly via natural language, with enforced read-only access and secure query limits. Supports SQLite and PostgreSQL, and works with any OpenAI-compatible model.0ISC
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to safely explore and query databases across SQLite, PostgreSQL, MySQL, and MSSQL, with schema introspection, natural language queries, and data profiling.MIT
TDQS
Scored across 3 tools
Each tool has a distinct role: capability discovery, pre-flight estimation, and bounded execution. However, estimate_query_cost and the internal estimating in run_query_bounded could cause slight confusion about when to use each, though descriptions clarify the difference.
All tool names use snake_case with a consistent verb_noun pattern (describe_, estimate_, run_). There are no deviations or mixed conventions.
Three tools form a minimal but focused set for a cost-guard server, each earning its place. The count sits at the low end of the typical 3-15 range, but is reasonable for the specialized scope.
The core lifecycle of advisory estimation and bounded execution is fully covered. There is a minor gap around tools for retrieving or setting quota/bound context, but agents can work around this for the stated purpose.