Azure MCP Server
All Azure MCP tools to create a seamless connection between AI agents and Azure services.
Update first. Issues have been reported, but none is flagged on the version the registry lists. That version can trail the package's newest release, so check you run one past the issues below.
Registry name com.microsoft/azure
· The registry calls this server version 3.0.0-beta.48, but the package it points to is 3.0.0-beta.48, 3.0.0b48. The package version is what gets installed, so that's the one we check. · Source code · Website
Reported issues
Each issue is counted once, with its other IDs listed under it. "Listed version" means the version the registry lists: "Not flagged" means OSV doesn't mark it as affected, and "Not checked" means the source gives no version we can compare.
| Issue | Severity | Listed version | Reported |
|---|---|---|---|
| GHSA-hhfx-wfvq-7g9cAzure MCP Server has Server-Side Request Forgery issue that allows authorized attacker to elevate privileges over a networkAlso filed as CVE-2026-26118, PYSEC-2026-2669 | high | Not flagged | Mar 10, 2026 |
Versions in the registry
3.0.0-beta.48 (package 3.0.0b48) (listed), 3.0.0-beta.47 (package 3.0.0b47), 3.0.0-beta.46 (package 3.0.0b46), 3.0.0-beta.45 (package 3.0.0b45), 3.0.0-beta.44 (package 3.0.0b44), 3.0.0-beta.43 (package 3.0.0b43), 3.0.0-beta.42 (package 3.0.0b42), 3.0.0-beta.41 (package 3.0.0b41), 3.0.0-beta.40 (package 3.0.0b40), 3.0.0-beta.39 (package 3.0.0b39), 3.0.0-beta.38 (package 3.0.0b38), 3.0.0-beta.37 (package 3.0.0b37), 3.0.0-beta.6, 2.0.2, 3.0.0-beta.5, 3.0.0-beta.4, 3.0.0-beta.3, 3.0.0-beta.2, 2.0.1, 2.0.0, 2.0.0-beta.40, 2.0.0-beta.39, 2.0.0-beta.38, 2.0.0-beta.37, 3.0.0-beta.1, 2.0.0-beta.36, 2.0.0-beta.35, 2.0.0-beta.34, 2.0.0-beta.33, 2.0.0-beta.32 and 15 older