Is Azure MCP Server safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highShell command built from a string (injection risk)
How Azure MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 60/100
- higher than 15% of 48,255 servers
Release history: 5 versions in the registry since 2026-09-16, latest 2026-09-30, typically one every 5 days.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
1 high2 medium
- Code scan2 source files scanned3/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (3)
- mediumnpm install lifecycle script present
install.script - highShell command built from a string (injection risk)
exec.shell-concatindex.js: …ation methods: ${npmErr.message}`) execSync(`${installCommand} --prefer-online`, instal… - mediumnpm install lifecycle script present
install.scriptpackage.json: …"3.0.0-beta.48" }, "scripts": { "postinstall": "node ./scripts/post-install-script.js"…
Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON