microsoft-teams-mcp@1.1.7
VERIFIED· install onlyPublisher claims: "Microsoft Teams meeting scheduler MCP tool using Microsoft Graph API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Install scripts ran; no agent task scenario for this bundle.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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
MS_CLIENT_SECRETConfiguration, not credentials: MS_CLIENT_ID, MS_TENANT_ID, MS_USER_ID- Where it talks to
- no vendor host named in the codeAlso microsoft.com, microsoftonline.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 with a scoped credential, under the guard, and read the third-party hosts first. The code names microsoft.com, microsoftonline.com as well as its own vendor. The guard injects MS_CLIENT_SECRET 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; install scripts ran; no agent task scenario for this bundle) on 2026-11-11 and scored it 89/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 · 2 scenarios · 0 deviationsStatic findings
raise ValueError("Environment variables missing. Pass credentials via main(credentials=...) or set MS_TENANT_ID, MS_CLIENT_ID, MS_CLIENT_SECRET, MS_USER_ID")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No other findings across 1,273 lines in 14 files.
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 microsoft-teams-mcp@1.1.7 as of 3d ago. This is the package itself, not its dependencies.