msteams-mcp@0.30.3
VERIFIED· not startedPublisher claims: "MCP server for Microsoft Teams - search messages, send replies, manage favourites" 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: 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 microsoft.com, office.com, microsoft.us, cloud.microsoft, microsoftonline.com, google.com, a.com, b.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
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. 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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 81/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 · 12 s · 2 scenarios · 0 deviationsStatic findings
{ key: 'polarbear', description: 'Polar bear 🐻❄️', category: 'animal' },Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.expect(isTeamsUrl('https://teams.microsoft.com/v2/#/conversations/19:[email protected]')).toBe(true);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.expect(sanitizeLinkUrl('file:///etc/passwd')).toBe('#');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.: 'Install Chrome from https://www.google.com/chrome/ or run: npx playwright install chromium';Fix: Pin versions and sources; vendor anything fetched at install time.// kill with signal 0 checks if process exists without killing itFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// Map to TranscriptEntry formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 msteams-mcp@0.30.3 as of 3d ago. This is the package itself, not its dependencies.