Ext Ops Panel
Open dashboard
Comparison

azure-cost-health-check vs HPSILab Quant Finance

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). HPSILab Quant Finance is an MCP server published by haiyunsky. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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-checkHPSILab Quant Finance
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.11.0
Downloads/month (PyPI): 379
Downloads/week (PyPI): 153
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.11.0
Downloads/month (PyPI): 379
Downloads/week (PyPI): 153
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 HPSILab Quant Finance
Factazure-cost-health-checkHPSILab Quant Finance
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/microsoft/azure-dev-toolsgithub.com/haiyunsky/hpsilab-quant-finance-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 32 h ago

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.

HPSILab Quant Finance

In its own words, on Official MCP Registry:

HPSILab Quant finance MCP for US stocks, ETFs, options, Monte Carlo, backtesting, and risk analysis.

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.

HPSILab Quant Finance As a remote MCP server

Claude Code
claude mcp add --transport http hpsilab-quant-finance-mcp https://hpsilab.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: HPSILAB_API_KEY (secret), Authorization header

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

Only HPSILab Quant Finance has a remote endpoint we check. How we check endpoints

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: HPSILab Quant Finance · 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. Package data comes from the Python Package Index (pypi.org). 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