Cost Guard MCP
PYPI · COST-GUARD-MCP · SCANNED SEP 20
Pre-flight query cost and result-size guardrails for AI agents on BigQuery, Snowflake, Databricks
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 5 of 77 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 493 tokens (~123/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Cost Guard MCP server?
Cost Guard MCP runs locally as a PyPI package, launched with uvx cost-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cost-guard-mcp
claude mcp add mcpsmiths-cost-guard-mcp -- uvx cost-guard-mcp
{
"mcpServers": {
"mcpsmiths-cost-guard-mcp": {
"command": "uvx",
"args": [
"cost-guard-mcp"
]
}
}
} {
"servers": {
"mcpsmiths-cost-guard-mcp": {
"command": "uvx",
"args": [
"cost-guard-mcp"
]
}
}
} codex mcp add mcpsmiths-cost-guard-mcp -- uvx cost-guard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcpsmiths-cost-guard-mcp": {
"type": "local",
"command": [
"uvx",
"cost-guard-mcp"
],
"enabled": true
}
}
} openclaw mcp add mcpsmiths-cost-guard-mcp --command uvx --arg cost-guard-mcp
mcp_servers:
mcpsmiths-cost-guard-mcp:
command: "uvx"
args: ["cost-guard-mcp"] {
"McpServers": {
"mcpsmiths-cost-guard-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"cost-guard-mcp"
]
}
}
} assistant mcp add mcpsmiths-cost-guard-mcp -t stdio -c uvx -a cost-guard-mcp
{
"mcpServers": {
"mcpsmiths-cost-guard-mcp": {
"command": "uvx",
"args": [
"cost-guard-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Package version: 0.2.0 → 0.3.0 functional
- 17 Sept 26 0
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 92 → 123 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.2.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Security disclosure: fail → pass ▲ functional
- Package version: 0.1.0 → 0.1.1 functional
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/cost-guard-mcp@0.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 77 packages
| Packages resolved | 77 |
|---|---|
| Stale | 4 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_credentials ~72
Verify credentials/connectivity for an engine without running any real query or dry-run estimate. Call this once after configuring a new engine (or when a real tool call fails) to get a fast, clear yes/no signal instead of debugging via trial queries.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | – |
| warehouse | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| engine | string | yes | – |
| ok | boolean | yes | – |
No examples provided.
describe_engine_capabilities ~61
Declare which cost signals are exact vs. approximate for the given warehouse engine. Call this before estimate_query_cost or run_query_bounded to understand how much to trust the accuracy_tier on their responses for this engine.
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| default_accuracy_tier | – | yes | – |
| engine | string | yes | – |
| known_gaps | array | – | – |
| supports_dollar_estimate | boolean | yes | – |
| supports_precise_bytes | boolean | yes | – |
No examples provided.
estimate_query_cost ~174
Estimate the cost of a SQL query before running it. ALWAYS call this before running an expensive-looking query. The response's accuracy_tier tells you how much to trust the number: PRECISE (exact), UPPER_BOUND (real cap, may overstate), HEURISTIC (rough). warehouse_size (Snowflake/Databricks only, e.g. "SMALL", "X-Large") and edition (Snowflake only, e.g. "enterprise") default to the smallest/standard tier if omitted — set them to match the warehouse you actually run this query on, or the dollar figure will understate cost on a larger warehouse.
| Name | Type | Req | Description |
|---|---|---|---|
| edition | – | – | – |
| engine | string | yes | – |
| sql | string | yes | – |
| warehouse | – | – | – |
| warehouse_size | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accuracy_tier | – | yes | – |
| caveats | array | – | – |
| currency | string | – | – |
| engine | string | yes | – |
| estimated_bytes | – | – | – |
| estimated_cost_usd | – | – | – |
No examples provided.
run_query_bounded ~186
Run a query only if its pre-flight cost estimate is within your given bounds; refuses otherwise (check result.status — "refused" means it did NOT run and result.hint explains why). NOTE: unlike estimate_query_cost, a successful call here has a real monetary/quota side effect — don't call this repeatedly without inspecting the result of each call. warehouse_size/edition (see estimate_query_cost) default to the smallest/standard tier if omitted - set them to match the warehouse you actually run on, since max_estimated_cost_usd is checked against the estimate they produce.
| Name | Type | Req | Description |
|---|---|---|---|
| edition | – | – | – |
| engine | string | yes | – |
| max_bytes_billed | – | – | – |
| max_estimated_cost_usd | – | – | – |
| max_rows | – | – | – |
| sql | string | yes | – |
| warehouse | – | – | – |
| warehouse_size | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| estimate | – | – | – |
| hint | – | – | – |
| reason | – | – | – |
| row_count | – | – | – |
| rows | – | – | – |
| status | string | yes | – |
No examples provided.
What is the Cost Guard MCP server?
Cost Guard MCP is listed in the public MCP registry as io.github.mcpsmiths/cost-guard-mcp. Pre-flight query cost and result-size guardrails for AI agents on BigQuery, Snowflake, Databricks. This page covers its PyPI package (cost-guard-mcp).
Is the Cost Guard MCP server safe to use?
Cost Guard MCP scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cost Guard MCP server expose?
Cost Guard MCP exposes 4 tools: check_credentials, describe_engine_capabilities, estimate_query_cost, run_query_bounded. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.
Is the Cost Guard MCP server still maintained?
Cost Guard MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.