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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to query Trino and Apache Pinot lakehouses under enforced governance, where every SQL statement is AST-validated, table-allowlisted, priced from the engine's own plan before it runs, and blocked or admitted against scan-byte and intermediate-row budgets. It also grounds agents with schema discovery tools, returns verified results with warnings instead of misleading answers, and records every tool call on an audit trail.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.15Apache 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
TDQS
Scored across 4 tools
Each tool targets a distinct stage: credential verification, capability/accuracy disclosure, cost estimation, and guarded execution. The overlap between estimate_query_cost and run_query_bounded is explicitly clarified by the side-effect warning.
All tool names use a consistent snake_case verb_noun pattern: check_, describe_, estimate_, run_. The slight grammatical extension in run_query_bounded does not break the overall naming consistency.
Four tools is well-scoped for a cost-guard MCP server. Each tool serves a necessary and non-redundant role in the pre-flight cost-protection workflow.
The core lifecycle is covered: verify connectivity, understand estimate reliability, estimate cost, and run only within bounds. A post-run actual-cost tracking or persistent budget management tool would be a minor enhancement, but agents can work around its absence for the stated use case.