microsoft-teams-mcp@0.8.7
CAUTION· static onlyPublisher claims: "Read Microsoft Teams data (every chat and channel, their messages, what is unread, inline images, and the Activity feed) from a shell with the fpx CLI (@fetchproxy/cli) instead of running the microsoft-teams-mcp server. A bearer token is captured once from a signed-in teams.cloud.microsoft tab, then Teams' own chat-service REST API is called with plain curl — the Activity feed included, as conversation 48:notifications. Use when you want Teams data without the MCP, in a script, or on a machine where the MCP isn't installed." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-09 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
chmod 700 "$dir" 2>/dev/nullFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.chmod 600 "$rc_file" 2>/dev/nullFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim chrischall: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.