Skills/ClawHub/microsoft-teams-mcp

microsoft-teams-mcp@0.7.0

CAUTION

Publisher 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.

Registry ClawHubPublisher chrischall · joined 8 days agoInstalls 1,087Last detonated 6 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-03 and scored it 65/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 only
t+CategoryObserved action

This 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

MEDIUM
File permission modification commandreferences/teams-env.sh:64 · File permission modification command — agent changes file ownership/permissionsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandreferences/teams-env.sh:28 · File permission modification command — agent changes file ownership/permissionsFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

What would make this Verified

15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. 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.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  3. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim chrischall