ms-graph-mcp@0.3.0
CAUTION· not startedPublisher claims: "Microsoft Graph MCP server — 85 tools across mail, calendar, meetings, Teams chat, files, search, people, directory, tasks and OneNote, over stdio or Streamable HTTP." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution 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
GRAPH_MCP_ACCESS_TOKENConfiguration, not credentials: DISPLAY, GRAPH_MCP_CACHE_DIR, GRAPH_MCP_FORCE_DEVICE_CODE, GRAPH_MCP_LOG_LEVEL, GRAPH_MCP_PORT, GRAPH_MCP_USER_EMAIL, GRAPH_MCP_WRITE_SCOPE, SSH_CONNECTION, SSH_TTY- Where it talks to
- no vendor host named in the codeAlso microsoft.com, microsoftonline.com, windows.net — 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names microsoft.com, microsoftonline.com, windows.net as well as its own vendor. The guard injects GRAPH_MCP_ACCESS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
validate_graph_id("../../etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.validate_mail_folder("../../etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# through a shell that would swallow it and force a 10-second kill on everyFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.env_file=("../.env.local", ".env"),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.A ``.env`` file in the working directory is loaded if present.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.application = mcp_server.streamable_http_app(Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# resp.json() cannot be used — graph_post_no_content exists for exactly thisFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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 ms-graph-mcp@0.3.0 as of 3d ago. This is the package itself, not its dependencies.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim nitin27may: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Destructive file system command detected≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.