npm not analyzable

@azure/mcp-win32-x64

v3.0.0-beta.19
npm

Azure MCP Server - Model Context Protocol implementation for Azure, for win32 on x64

maintainer
azure-sdk
license
MIT
first seen
2026-06-09
last seen
2026-06-17
releases · 30d
11
short id
risk insufficient evidence

Insufficient evidence to grade. This server's source has not been statically analyzed, so a low grade would only mean "nothing found", not "nothing there". We don't show a reassuring grade we can't stand behind. Attested signals (CVEs, provenance) below still apply.

Once the source is analyzed (see the analysis flag in the header), a graded score appears here. How analysis works: methodology.

graded 15m ago · see ecosystem CVEs →

vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety all quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@azure/mcp-win32-x64/badge.svg)](https://mcpobservatory.com/servers/npm:@azure/mcp-win32-x64/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of azure-sdk.