Home / MCP registry index / Topics / Azure

Azure MCP servers, with their tools checked

Every server in the official MCP registry that mentions Azure, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.

12 listed. We have read the tools of 1 so far; the others want credentials first, could not be reached, or are still waiting for their first read.

Infrastructure servers can change live systems. Check which tools write, deploy or delete before you connect one with real credentials.

io.tooloracle/cloudoracle io.tooloracle/cloudoracle	14 tools, nothing matched 2026-10-22
ai.levelfour/levelfour-mcp ai.levelfour/levelfour-mcp	needs credentials to list tools 2026-10-22
Mobula cloud.mobula/mobula	not read yet
CloudQuell com.cloudquell/cloudquell-mcp-server	not read yet
BranchDeploy dev.branch-deploy/branchdeploy	not read yet
GPU Cloud Prices (AWS, Azure, OCI) eu.runlocal.gpu0a49b9444d66-s-org/gpu-prices	not read yet
GPU Cloud Prices (AWS, Azure, OCI) eu.runlocal.wise-shrimp/gpu-prices	not read yet
Control Plane io.cpln/control-plane	not read yet
Cloud FinOps Skill & MCP io.github.OptimNow/cloud-finops	not read yet
DevOps Agent io.github.shittuay/devops-agent	not read yet
io.github.vdionisopoulos/azure-vm-pricing io.github.vdionisopoulos/azure-vm-pricing	not read yet
io.quanti/mcp-server io.quanti/mcp-server	not read yet

Choosing one

Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 1 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.