io.github.vdionisopoulos/azure-vm-pricing
NPM · AZURE-VM-PRICING-MCP · 2 COMPONENTS
Azure VM sizes and USD list prices in 24 regions, updated weekly. Find, price and compare VMs.
Available components
Last scanned (1 hour ago)
Scores higher than 48% of npm servers
Category Cloud Infrastructure
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 569 tokens (~142/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- CVE-2023-54404 affects this package: high ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
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 5 Nov 2026 · Analysed npm/azure-vm-pricing-mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
estimate_vm_cost Estimate Azure VM cost ~167
Monthly and yearly cost of one or more Azure VM sizes for pay as you go, reservations and savings plans, with the break-even hours per month for each commitment. Use it to compare sizes or regions.
| Name | Type | Req | Description |
|---|---|---|---|
| hours_per_month | number | – | Runtime hours per month. Default 730 (always on). |
| instances | integer | – | Number of VMs. Default 1. |
| os | string | – | Operating system for pay-as-you-go prices. Default linux. |
| region | string | – | Azure region, e.g. westeurope or "West Europe". Omit to use each size's cheapest region. |
| sizes | array | yes | One to five VM sizes to price, e.g. ["Standard_D4s_v5", "Standard_D4as_v6"]. |
No output schema declared.
No examples provided.
find_vm_sizes Find Azure VM sizes ~271
Find the cheapest Azure VM sizes that meet vCPU, memory and workload requirements, with monthly USD list prices. Burstable (B-series) and confidential sizes are only included when that workload is requested.
| Name | Type | Req | Description |
|---|---|---|---|
| arch | string | – | CPU architecture. |
| max_results | integer | – | Default 10. |
| min_gpus | integer | – | Minimum number of whole GPUs (partitioned GPUs such as 1/6 A10 do not count). |
| min_memory_gib | number | – | Minimum memory in GiB, e.g. 32. |
| min_vcpus | integer | – | Minimum vCPUs, e.g. 8. |
| need_temp_disk | boolean | – | Only sizes with a local temporary disk. |
| os | string | – | Operating system for pay-as-you-go prices. Default linux. |
| region | string | – | Azure region, e.g. westeurope or "West Europe". Omit to use each size's cheapest region. |
| sort | string | – | price = cheapest first (default); fit = least spare vCPU/memory first. |
| workload | string | – | Workload family. ai = NVIDIA GPUs only (CUDA, PyTorch, vLLM); gpu = any GPU incl. AMD. Omit for any (excludes burstable and confidential). |
No output schema declared.
No examples provided.
get_price_changes Azure VM price changes ~48
Weekly report of new Azure VM sizes, retired sizes and the biggest list-price moves across 24 regions.
| Name | Type | Req | Description |
|---|---|---|---|
| weeks | integer | – | How many weekly reports, newest first. Default 1. |
No output schema declared.
No examples provided.
get_vm_size Azure VM size details ~83
Specs of one Azure VM size and its hourly USD prices per region (Linux, Windows, 1/3-year reservations, 1/3-year savings plans), cheapest region first.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | Limit prices to one region. |
| size | string | yes | VM size, e.g. Standard_D4s_v5 or D4s v5. |
No output schema declared.
No examples provided.
How do I install the io.github.vdionisopoulos/azure-vm-pricing MCP server?
io.github.vdionisopoulos/azure-vm-pricing runs locally as an npm package, launched with npx -y azure-vm-pricing-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · azure-vm-pricing-mcp
claude mcp add vdionisopoulos-azure-vm-pricing -- npx -y azure-vm-pricing-mcp
What is the io.github.vdionisopoulos/azure-vm-pricing MCP server?
io.github.vdionisopoulos/azure-vm-pricing is an MCP server listed in the public MCP registry as io.github.vdionisopoulos/azure-vm-pricing. Azure VM sizes and USD list prices in 24 regions, updated weekly. Find, price and compare VMs. This page covers its npm package (azure-vm-pricing-mcp).
Is the io.github.vdionisopoulos/azure-vm-pricing MCP server safe to use?
io.github.vdionisopoulos/azure-vm-pricing scores 74 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.vdionisopoulos/azure-vm-pricing MCP server expose?
io.github.vdionisopoulos/azure-vm-pricing exposes 4 tools: find_vm_sizes, get_vm_size, estimate_vm_cost, get_price_changes. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.
Is the io.github.vdionisopoulos/azure-vm-pricing MCP server still maintained?
io.github.vdionisopoulos/azure-vm-pricing is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vdionisopoulos/azure-vm-pricing MCP server under?
io.github.vdionisopoulos/azure-vm-pricing declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.