@chrischall/microsoft-teams-mcp

MCPattested
v0.2.0io.github.chrischallMITUpdated 2d agonpmGitHub

Microsoft Teams for Claude — read your chats, teams, channels, and open messages, via your browser

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
248Downloads/wk
2d agoLast update
Package
Authorio.github.chrischall
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
npm@chrischall/microsoft-teams-mcp
GitHubchrischall/microsoft-teams-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 33040bf
Dependencies✓ 8 resolved · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.2.0 · 1d agoHow well does this scan work?
EvalsNone
IndexedSep 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged
Statically extracted from the published packagev0.2.0 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

teams_get_activityList the rows in the Activity feed (the bell icon in the left nav) — mentions,

List the rows in the Activity feed (the bell icon in the left nav) — mentions,

No input schema was published for this tool.

teams_list_teams_and_channelsList the Teams the signed-in user belongs to and their channels, from the

List the Teams the signed-in user belongs to and their channels, from the

No input schema was published for this tool.

teams_get_open_channel_postsRead the top-level posts in whichever Teams CHANNEL is CURRENTLY OPEN in the

Read the top-level posts in whichever Teams CHANNEL is CURRENTLY OPEN in the

No input schema was published for this tool.

teams_list_chatsList the chats in the signed-in user's Teams chat sidebar (1:1s, group chats, meeting

List the chats in the signed-in user's Teams chat sidebar (1:1s, group chats, meeting

No input schema was published for this tool.

teams_get_open_chat_messagesRead the message thread of whichever Teams chat is CURRENTLY OPEN in the user's

Read the message thread of whichever Teams chat is CURRENTLY OPEN in the user's

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Microsoft Teams for Claude — read your chats, teams, channels, and open messages, via your browser

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-23 — observed resolution, not a publisher declaration.

8 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.