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.jasonwilbur/cloud-regions

NPM · MCP-SERVER-CLOUD-REGIONS · SCANNED SEP 20

Cloud region data for AWS, Azure, GCP, OCI & more. Query by location, compliance, GPU.

−1 this week 83 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 878 tokens (~62/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Install

How do I install the io.github.jasonwilbur/cloud-regions MCP server?

io.github.jasonwilbur/cloud-regions runs locally as an npm package, launched with npx -y mcp-server-cloud-regions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mcp-server-cloud-regions

# add to Claude Code
claude mcp add jasonwilbur-cloud-regions -- npx -y mcp-server-cloud-regions
// .cursor/mcp.json
{
  "mcpServers": {
    "jasonwilbur-cloud-regions": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-cloud-regions"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "jasonwilbur-cloud-regions": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-cloud-regions"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add jasonwilbur-cloud-regions -- npx -y mcp-server-cloud-regions
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jasonwilbur-cloud-regions": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-cloud-regions"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jasonwilbur-cloud-regions --command npx --arg -y --arg mcp-server-cloud-regions
# ~/.hermes/config.yaml
mcp_servers:
  jasonwilbur-cloud-regions:
    command: "npx"
    args: ["-y", "mcp-server-cloud-regions"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "jasonwilbur-cloud-regions": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-cloud-regions"
      ]
    }
  }
}
# add to Vellum
assistant mcp add jasonwilbur-cloud-regions -t stdio -c npx -a -y mcp-server-cloud-regions
// mcp.json
{
  "mcpServers": {
    "jasonwilbur-cloud-regions": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-cloud-regions"
      ]
    }
  }
}
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.

  • 18 Sept 26 +1

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

  • 16 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
  • 6 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/mcp-server-cloud-regions@1.0.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 →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~878 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
compare_provider_coverage ~70

Compare how many regions each provider has in a specific country or continent

NameTypeReqDescription
continentstringContinent to compare (e.g., "europe", "asia")
countryCodestringISO country code to compare (e.g., "US", "DE", "JP")

No output schema declared.

No examples provided.

find_compliant_regions ~73

Find regions that have specific compliance certifications (e.g., HIPAA, FedRAMP, GDPR, SOC2)

NameTypeReqDescription
certificationsarrayyesRequired compliance certifications. Regions must have ALL specified certifications.
countryCodesarrayFilter by country codes
providersarrayFilter by provider IDs

No output schema declared.

No examples provided.

find_gpu_regions ~80

Find regions with GPU availability, optionally filtering by GPU type (e.g., A100, H100, TPU)

NameTypeReqDescription
continentsarrayFilter by continent
gpuTypestringFilter by GPU type (e.g., "A100", "H100", "TPU")
providersarrayFilter by provider IDs

No output schema declared.

No examples provided.

find_nearby_regions ~98

Find cloud regions nearest to a geographic location. Useful for latency optimization and data residency planning.

NameTypeReqDescription
hasGpubooleanFilter to only regions with GPU
latitudenumberyesTarget latitude
limitnumberMaximum number of results to return
longitudenumberyesTarget longitude
maxDistanceKmnumberMaximum distance in kilometers
providersarrayFilter by provider IDs

No output schema declared.

No examples provided.

find_sustainable_regions ~39

Find carbon neutral and sustainable cloud regions

NameTypeReqDescription
continentsarrayFilter by continent
providersarrayFilter by provider IDs

No output schema declared.

No examples provided.

get_data_info ~30

Get metadata about the region data including last updated date, total counts, and source URLs for each provider

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_provider_regions ~53

Get all regions for a specific cloud provider

NameTypeReqDescription
providerstringyesProvider ID (e.g., "aws", "azure", "gcp", "oci", "digitalocean", "crusoe")

No output schema declared.

No examples provided.

get_region ~51

Get detailed information about a specific cloud region by its ID

NameTypeReqDescription
idstringyesRegion ID (e.g., "aws-us-east-1", "azure-eastus", "gcp-us-central1")

No output schema declared.

No examples provided.

get_statistics ~29

Get summary statistics about all cloud regions, including counts by provider, country, continent, and special capabilities.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_cities ~24

List all cities that have cloud regions, with the providers present in each

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_countries ~24

List all countries that have cloud regions, with count of regions in each

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_providers ~28

List all cloud providers with their metadata

NameTypeReqDescription
tierstringFilter by provider tier

No output schema declared.

No examples provided.

list_regions ~229

List all cloud regions across all providers. Supports filtering by provider, tier, country, continent, compliance, sustainability, GPU availability, and more.

NameTypeReqDescription
carbonNeutralbooleanFilter to only carbon neutral regions
compliancearrayFilter by compliance certifications (e.g., ["HIPAA", "GDPR", "SOC2"])
continentsarrayFilter by continent
countryCodesarrayFilter by ISO country codes (e.g., ["US", "DE", "JP"])
dataResidencystringFilter by data residency (e.g., "EU", "US", "Germany")
hasGpubooleanFilter to only regions with GPU availability
minAvailabilityZonesnumberFilter by minimum number of availability zones
providersarrayFilter by provider IDs (e.g., ["aws", "azure", "gcp"])
regionTypesarrayFilter by region type (e.g., ["commercial", "government", "sovereign"])
tiersarrayFilter by provider tier

No output schema declared.

No examples provided.

search_regions ~50

Search regions by text query. Searches display name, region code, city, country, and provider name.

NameTypeReqDescription
providersarrayFilter by provider IDs
querystringyesSearch query text

No output schema declared.

No examples provided.

Common questions

What is the io.github.jasonwilbur/cloud-regions MCP server?

io.github.jasonwilbur/cloud-regions is an MCP server listed in the public MCP registry as io.github.jasonwilbur/cloud-regions. Cloud region data for AWS, Azure, GCP, OCI & more. Query by location, compliance, GPU. This page covers its npm package (mcp-server-cloud-regions).

Is the io.github.jasonwilbur/cloud-regions MCP server safe to use?

io.github.jasonwilbur/cloud-regions scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.jasonwilbur/cloud-regions MCP server expose?

io.github.jasonwilbur/cloud-regions exposes 14 tools: list_regions, get_region, list_providers, get_provider_regions, find_nearby_regions, and 9 more. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.

Is the io.github.jasonwilbur/cloud-regions MCP server still maintained?

io.github.jasonwilbur/cloud-regions is still listed as active in the MCP registry. We last reached this channel on 20 September 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.jasonwilbur/cloud-regions MCP server under?

io.github.jasonwilbur/cloud-regions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.