mcp@4.0.0-beta.7
VERIFIED· startup onlyPublisher claims: "Azure MCP Server - Model Context Protocol implementation for Azure" Observed in sandbox: calls registry.npmjs.org only, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso aka.ms — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · reached only registry.npmjs.org
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: calls registry.npmjs.org only, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 3 scenariosStatic findings
…oft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your a…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.console.error(` npx -y ${packageName}@latest --version`)Fix: Pin versions and sources; vendor anything fetched at install time.console.error(`\n3. If using npx, clear the npx cache and try again:`)Fix: Pin versions and sources; vendor anything fetched at install time.console.error(` npx -y clear-npx-cache`)Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @azure/mcp@4.0.0-beta.7 as of 3d ago. This is the package itself, not its dependencies.