mcp-microsoft-graph-auth@0.1.2
VERIFIED· install onlyPublisher claims: "Shared Microsoft Graph auth helpers (Device Code, token cache, BYO client) for MCP servers." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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 microsoftonline.com, microsoft.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. 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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-08 and scored it 82/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: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
`~/.ssh/id_rsa`: trust the local user account.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`~/.ssh/id_rsa`: trust the local user account.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`npm login`, `~/.ssh/id_rsa`: trust the local user account.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.chmod 600 ~/.cache/mcp-microsoft-graph-auth/harness/token.jsonFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…at this repo is A **shared library** of Microsoft Graph auth helpers used by [`mcp-server-sharepoint`](https://github.com/XMV-Solutions-GmbH/sharepoint-mcp) and [`mcp-server-outlook`](https://github.com/XMV-Solutions-GmbH/outlook-mcp). Own…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.`npm login`, `~/.ssh/id_rsa`: trust the local user account.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for mcp-microsoft-graph-auth@0.1.2 as of 6d ago. This is the package itself, not its dependencies.