Microsoft 365 Teams
NPM · @MINDSTONE/MCP-SERVER-MICROSOFT-TEAMS · SCANNED SEP 20
Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 35 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mindstone/mcp-servers). View diagnostics → Pass
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 40 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability48
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 967 tokens (~53/item across 18 items; 17 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Microsoft 365 Teams MCP server?
Microsoft 365 Teams runs locally as an npm package, launched with npx -y @mindstone/mcp-server-microsoft-teams. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mindstone/mcp-server-microsoft-teams
claude mcp add mindstone-mcp-server-microsoft-teams -- npx -y @mindstone/mcp-server-microsoft-teams
{
"mcpServers": {
"mindstone-mcp-server-microsoft-teams": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-microsoft-teams"
]
}
}
} {
"servers": {
"mindstone-mcp-server-microsoft-teams": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-microsoft-teams"
]
}
}
} codex mcp add mindstone-mcp-server-microsoft-teams -- npx -y @mindstone/mcp-server-microsoft-teams
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-microsoft-teams": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-microsoft-teams"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-microsoft-teams --command npx --arg -y --arg @mindstone/mcp-server-microsoft-teams
mcp_servers:
mindstone-mcp-server-microsoft-teams:
command: "npx"
args: ["-y", "@mindstone/mcp-server-microsoft-teams"] {
"McpServers": {
"mindstone-mcp-server-microsoft-teams": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mindstone/mcp-server-microsoft-teams"
]
}
}
} assistant mcp add mindstone-mcp-server-microsoft-teams -t stdio -c npx -a -y @mindstone/mcp-server-microsoft-teams
{
"mcpServers": {
"mindstone-mcp-server-microsoft-teams": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-microsoft-teams"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@mindstone/mcp-server-microsoft-teams@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mindstone/mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mindstone/mcp-servers/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2406248748 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5353da0fdebb512ad3609baed70939ddf8e8d00c4c31191b7c1bef526930f2eb1f5bd881d963762c0ff8631f2013a7188429e623b124eeea08ab343a2 |
Background: How many MCP packages publish verified provenance →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 35 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compose_chat_message ~111
Open an inline editable message compose form before sending to a Teams chat. Use this when the user wants to write or send a Teams message so they can review and edit it first. Does NOT send directly — the form posts the message (via send_chat_message) when the user clicks Send. PARAMETERS: target (the chat ID to send to), text (message content).
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | The chat ID to send the message to |
| text | string | yes | Message content (HTML supported) |
No output schema declared.
No examples provided.
create_chat ~92
Create a new 1:1 or group chat with one or more colleagues (by email address or user ID) and return the new chat ID, which can then be used with send_chat_message.
| Name | Type | Req | Description |
|---|---|---|---|
| members | array | yes | Email addresses or user IDs of the other participants (one for a 1:1 chat, several for a group chat) |
| topic | string | – | Chat topic (group chats only) |
No output schema declared.
No examples provided.
find_user ~64
Look up people in the organization by display name or email address. Use this to resolve a colleague to a user ID or email before creating a chat. Requires the User.ReadBasic.All Graph permission.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Display name or email address of the person to find |
No output schema declared.
No examples provided.
get_chat ~25
Get details about a specific chat.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | Chat ID |
No output schema declared.
No examples provided.
get_presence ~22
Get your current presence status (available, busy, away, etc.).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_user_presence ~58
Get a colleague's current presence status (available, busy, in a meeting, etc.). Requires the Presence.Read.All Graph permission, which may need tenant admin approval.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | User ID or email address of the colleague |
No output schema declared.
No examples provided.
list_channel_messages ~74
List recent messages in a Teams channel. Requires the ChannelMessage.Read.All Graph permission, which may need tenant admin approval.
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | string | yes | Channel ID |
| teamId | string | yes | Team ID |
| top | number | – | Max messages to return (default: 25, max: 50) |
No output schema declared.
No examples provided.
list_channels ~24
List channels in a Team.
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | yes | Team ID |
No output schema declared.
No examples provided.
list_chat_messages ~47
Get recent messages from a chat.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | Chat ID |
| top | number | – | Max messages to return (default: 50, max: 50) |
No output schema declared.
No examples provided.
list_chats ~45
List recent Teams chats (1:1, group, and meeting chats).
| Name | Type | Req | Description |
|---|---|---|---|
| top | number | – | Max chats to return (default: 25, max: 50) |
No output schema declared.
No examples provided.
list_teams ~17
List Teams you are a member of.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reply_to_channel_message ~83
Reply to an existing message in a Teams channel. Requires the ChannelMessage.Send Graph permission, which may need tenant admin approval.
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | string | yes | Channel ID |
| content | string | yes | Reply content (HTML supported) |
| messageId | string | yes | ID of the channel message to reply to |
| teamId | string | yes | Team ID |
No output schema declared.
No examples provided.
reply_to_message ~61
Reply to a specific message in a chat, creating a threaded reply.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | Chat ID |
| content | string | yes | Reply content (HTML supported) |
| messageId | string | yes | ID of the chat message to reply to |
No output schema declared.
No examples provided.
search_messages ~56
Search Teams chat and channel messages by keyword across conversations you can access.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text (keyword or phrase) |
| top | number | – | Max results to return (default: 10, max: 25) |
No output schema declared.
No examples provided.
send_channel_message ~65
Post a new message to a Teams channel. Requires the ChannelMessage.Send Graph permission, which may need tenant admin approval.
| Name | Type | Req | Description |
|---|---|---|---|
| channelId | string | yes | Channel ID |
| content | string | yes | Message content (HTML supported) |
| teamId | string | yes | Team ID |
No output schema declared.
No examples provided.
send_chat_message ~38
Send a message to a chat.
| Name | Type | Req | Description |
|---|---|---|---|
| chatId | string | yes | Chat ID |
| content | string | yes | Message content (HTML supported) |
No output schema declared.
No examples provided.
set_presence ~80
Set your own presence status (e.g. Busy, DoNotDisturb, Away), optionally for a limited duration. Requires the Presence.ReadWrite Graph permission.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | yes | Presence availability to set |
| durationMinutes | integer | – | How long the status applies, in whole minutes (5-480). Omit to keep it until changed. |
No output schema declared.
No examples provided.
What is the Microsoft 365 Teams MCP server?
Microsoft 365 Teams is an MCP server listed in the public MCP registry as io.github.mindstone/mcp-server-microsoft-teams. Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence. This page covers its npm package (@mindstone/mcp-server-microsoft-teams).
Is the Microsoft 365 Teams MCP server safe to use?
Microsoft 365 Teams scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Microsoft 365 Teams MCP server expose?
Microsoft 365 Teams exposes 17 tools: list_chats, get_chat, list_chat_messages, compose_chat_message, send_chat_message, and 12 more. Their descriptions and schemas cost roughly 962 tokens of context every time the server is loaded.
Is the Microsoft 365 Teams MCP server still maintained?
Microsoft 365 Teams is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Microsoft 365 Teams MCP server under?
Microsoft 365 Teams declares the FSL-1.1-MIT licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.