Ext Ops Panel
Open dashboard
Comparison

azure-cost-health-check vs Cost Guard MCP

azure-cost-health-check is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Cost Guard MCP is an MCP server published by mcpsmiths. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceazure-cost-health-checkCost Guard MCP
Copilot CLI: github/awesome-copilot Listed
Version: 0.4.5
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.2
Downloads/month (PyPI): 777
Downloads/week (PyPI): 165
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

azure-cost-health-check vs Cost Guard MCP
Factazure-cost-health-checkCost Guard MCP
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (cost-guard-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published12, secrets among them: 6
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/azure-dev-toolsgithub.com/mcpsmiths/cost-guard-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

azure-cost-health-check

In its own words, on Copilot CLI: github/awesome-copilot:

Read-only Azure cost, forecasts, budget alerts, Advisor recommendations, and AI billing analysis in a Copilot canvas.

Cost Guard MCP

In its own words, on Official MCP Registry:

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

How to run each

azure-cost-health-check

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Cost Guard MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DATABRICKS_CLIENT_SECRET=<YOUR_DATABRICKS_CLIENT_SECRET>" --env "DATABRICKS_TOKEN=<YOUR_DATABRICKS_TOKEN>" --env "GOOGLE_APPLICATION_CREDENTIALS=<YOUR_GOOGLE_APPLICATION_CREDENTIALS>" --env "SNOWFLAKE_PASSWORD=<YOUR_SNOWFLAKE_PASSWORD>" --env "SNOWFLAKE_PRIVATE_KEY_PASSPHRASE=<YOUR_SNOWFLAKE_PRIVATE_KEY_PASSPHRASE>" --env "SNOWFLAKE_PRIVATE_KEY_PATH=<YOUR_SNOWFLAKE_PRIVATE_KEY_PATH>" --transport stdio cost-guard-mcp -- uvx cost-guard-mcp

Requires: DATABRICKS_CLIENT_SECRET (secret), DATABRICKS_TOKEN (secret), GOOGLE_APPLICATION_CREDENTIALS (secret), SNOWFLAKE_PASSWORD (secret), SNOWFLAKE_PRIVATE_KEY_PASSPHRASE (secret), SNOWFLAKE_PRIVATE_KEY_PATH (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of azure-cost-health-check publish no settings it asks for, so we do not compare settings.

What it can do: azure-cost-health-check · What it can do: Cost Guard MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built