Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.vdionisopoulos/azure-vm-pricing

REMOTE · CLD2DAY.COM · 2 COMPONENTS

Azure VM sizes and USD list prices in 24 regions, updated weekly. Find, price and compare VMs.

+3 this week 82 Trust /100

Last scanned (21 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 653 tokens (~163/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
  • 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 5 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
Changelog

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.

  • 3 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.

  • 1 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.

  • 30 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.

  • 28 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.

  • 25 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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 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.

  • 20 Oct 26 +47
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • HTTPS: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Authorization: fail → partial ▲ security
    • Endpoint reachability: behind authorisation → reachable ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
Diagnostics

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 4 Nov 2026 · Probed https://cld2day.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cld2day.com CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 19 Oct 2026 19 Apr 2027 RSA 2048 SHA256-RSA 4a80ce77c6e237796900134ed551bef
SANs: cld2day.com
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of cld2day.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cld2day.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://cld2day.com/mcp Verified 200
http (plaintext) http://cld2day.com/mcp HTTPS enforced 301 https://cld2day.com/mcp
MCP tools · 4 exposed · ~557 tokens

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 →

Tool Tokens
estimate_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.

NameTypeReqDescription
hours_per_monthnumber–Runtime hours per month. Default 730 (always on).
instancesinteger–Number of VMs. Default 1.
osstring–Operating system for pay-as-you-go prices. Default linux.
regionstring–Azure region, e.g. westeurope or "West Europe". Omit to use each size's cheapest region.
sizesarrayyesOne to five VM sizes to price, e.g. ["Standard_D4s_v5", "Standard_D4as_v6"].
NameTypeReqDescription
cheapeststring––
dataSourceobjectyespricesAsOf (ISO date), currency, source, dataset, stale (true if the weekly refresh is late).
estimatesarray––
hoursPerMonthnumber––
optionsarray––
regionstring––
sizestring––

No examples provided.

find_vm_sizes ~259

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.

NameTypeReqDescription
archstring–CPU architecture.
max_resultsinteger–Default 10.
min_gpusinteger–Minimum number of whole GPUs (partitioned GPUs such as 1/6 A10 do not count).
min_memory_gibnumber–Minimum memory in GiB.
min_vcpusinteger–Minimum vCPUs.
need_temp_diskboolean–Only sizes with a local temporary disk.
osstring–Operating system for pay-as-you-go prices. Default linux.
regionstring–Azure region, e.g. westeurope or "West Europe". Omit to use each size's cheapest region.
sortstring–price = cheapest first (default); fit = least spare vCPU/memory first.
workloadstring–Workload family. ai = NVIDIA GPUs only (CUDA, PyTorch, vLLM); gpu = any GPU incl. AMD. Omit for any (excludes burstable and confidential).
NameTypeReqDescription
dataSourceobjectyespricesAsOf (ISO date), currency, source, dataset, stale (true if the weekly refresh is late).
matchCountintegeryes–
osstring––
pricedInstring––
resultsarrayyes–

No examples provided.

get_price_changes ~48

Weekly report of new Azure VM sizes, retired sizes and the biggest list-price moves across 24 regions.

NameTypeReqDescription
weeksinteger–How many weekly reports, newest first. Default 1.
NameTypeReqDescription
dataSourceobjectyespricesAsOf (ISO date), currency, source, dataset, stale (true if the weekly refresh is late).
messagestring––
reportsarray––

No examples provided.

get_vm_size ~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.

NameTypeReqDescription
regionstring–Limit prices to one region.
sizestringyesVM size, e.g. Standard_D4s_v5 or D4s v5.
NameTypeReqDescription
categorystring––
dataSourceobjectyespricesAsOf (ISO date), currency, source, dataset, stale (true if the weekly refresh is late).
memoryGiBnumber––
pricesarrayyesHourly USD prices per region, cheapest first.
sizestringyes–
urlstring––
vcpusinteger––

No examples provided.

Install

How do I install the io.github.vdionisopoulos/azure-vm-pricing MCP server?

io.github.vdionisopoulos/azure-vm-pricing is a hosted endpoint at https://cld2day.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · cld2day.com

# add to Claude Code
claude mcp add --transport http vdionisopoulos-azure-vm-pricing 'https://cld2day.com/mcp'
Common questions

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 hosted endpoint (https://cld2day.com/mcp).

Is the io.github.vdionisopoulos/azure-vm-pricing MCP server safe to use?

io.github.vdionisopoulos/azure-vm-pricing scores 82 out of 100 on VerifyMCP. 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 557 tokens of context every time the server is loaded.

Does the io.github.vdionisopoulos/azure-vm-pricing MCP server require authentication?

No. We connected to io.github.vdionisopoulos/azure-vm-pricing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.