cost-guard-mcp

MCPcommunity
v0.3.2io.github.mcpsmithsUnknownUpdated 6d agoGitHub

Pre-flight query cost and result-size guardrails for AI agents on BigQuery, Snowflake, Databricks

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
6d agoLast update
Reads these credentials
  • GOOGLE_APPLICATION_CREDENTIALSAPI keyoptional

    BigQuery: path to a service-account key file (Application Default Credentials). Required to use the bigquery engine.

  • SNOWFLAKE_PRIVATE_KEY_PATHAPI keyoptional

    Snowflake: path to an RSA private key file for key-pair auth (preferred over SNOWFLAKE_PASSWORD). Either this or SNOWFLAKE_PASSWORD is required to use the snowflake engine.

  • SNOWFLAKE_PRIVATE_KEY_PASSPHRASEAPI keyoptional

    Snowflake: passphrase for an encrypted SNOWFLAKE_PRIVATE_KEY_PATH key file, if the key is encrypted.

  • SNOWFLAKE_PASSWORDAPI keyoptional

    Snowflake: password (discouraged; prefer SNOWFLAKE_PRIVATE_KEY_PATH). Either this or SNOWFLAKE_PRIVATE_KEY_PATH is required to use the snowflake engine.

  • DATABRICKS_TOKENAPI keyoptional

    Databricks: personal access token (simplest auth option). Either this or DATABRICKS_CLIENT_ID + DATABRICKS_CLIENT_SECRET is required to use the databricks engine.

  • DATABRICKS_CLIENT_SECRETOAuth appoptional

    Databricks: OAuth machine-to-machine service-principal client secret. Requires DATABRICKS_CLIENT_ID as well.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.mcpsmiths
LicenseUnknown
Version0.3.2
Sourcemcp-registry
GitHubmcpsmiths/cost-guard-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.2.0 · 16d agoHow well does this scan work?
EvalsNone
IndexedSep 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source16d ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Pre-flight query cost and result-size guardrails for AI agents on BigQuery, Snowflake, Databricks

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.