io.github.SuperAngryMonkey/iris
PYPI · IRIS-MCP · SCANNED SEP 20
Microsoft 365 mail MCP: drafts into Outlook; sending off by default, opt-in via IRIS_ENABLE_SEND.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 37 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 536 tokens (~67/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "iris_delete_draft" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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 io.github.SuperAngryMonkey/iris MCP server?
io.github.SuperAngryMonkey/iris runs locally as a PyPI package, launched with uvx iris-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · iris-mcp
claude mcp add superangrymonkey-iris -- uvx iris-mcp
{
"mcpServers": {
"superangrymonkey-iris": {
"command": "uvx",
"args": [
"iris-mcp"
]
}
}
} {
"servers": {
"superangrymonkey-iris": {
"command": "uvx",
"args": [
"iris-mcp"
]
}
}
} codex mcp add superangrymonkey-iris -- uvx iris-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"superangrymonkey-iris": {
"type": "local",
"command": [
"uvx",
"iris-mcp"
],
"enabled": true
}
}
} openclaw mcp add superangrymonkey-iris --command uvx --arg iris-mcp
mcp_servers:
superangrymonkey-iris:
command: "uvx"
args: ["iris-mcp"] {
"McpServers": {
"superangrymonkey-iris": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"iris-mcp"
]
}
}
} assistant mcp add superangrymonkey-iris -t stdio -c uvx -a iris-mcp
{
"mcpServers": {
"superangrymonkey-iris": {
"command": "uvx",
"args": [
"iris-mcp"
]
}
}
} 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.
- 20 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.
- 17 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.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 pypi/iris-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 37 packages
| Packages resolved | 37 |
|---|---|
| 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 →
iris_auth_status ~24
Report whether iris is signed in, as whom, and with what scopes.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_create_draft ~154
Compose a message into a mail folder as an unsent draft. It is NOT sent — a human opens Outlook and presses Send. folder selects the destination folder by display name, created on first use if absent. Omit it to use the configured default (IRIS_DRAFT_FOLDER, currently "AI Drafts"); pass "" or "Drafts" for the normal Outlook Drafts folder. Set reply_to_message_id to draft a threaded reply.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | – |
| body | string | yes | – |
| cc | – | – | – |
| folder | – | – | – |
| html | boolean | – | – |
| reply_to_message_id | – | – | – |
| subject | string | yes | – |
| to | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_delete_draft ~53
Delete a draft. Destructive, so confirm=true is required — set it only after the human has explicitly approved deleting this specific draft.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| draft_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_list_drafts ~70
List recent messages sitting in a draft folder. folder selects which one by display name; omit it for the configured default (IRIS_DRAFT_FOLDER), or pass "" / "Drafts" for the normal Outlook Drafts folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | – | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_list_folders ~53
List the mailbox's top-level mail folders (name, id, unread/total counts) so you can pick one to pass as the `folder` argument to iris_create_draft or iris_list_drafts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_login ~56
Start a device-code sign-in for the mailbox. Returns a URL and a code for the human to enter in a browser; then call iris_login_finish() to complete. Only needed once, or after the refresh token lapses.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_login_finish ~59
Complete a device-code sign-in started with iris_login(). Call after entering the code in the browser. Waits up to ~60s; if the code has not been entered yet, it says so and can simply be called again.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
iris_update_draft ~67
Revise an existing draft in place. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | – |
| body | – | – | – |
| cc | – | – | – |
| draft_id | string | yes | – |
| html | boolean | – | – |
| subject | – | – | – |
| to | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.SuperAngryMonkey/iris MCP server?
io.github.SuperAngryMonkey/iris is an MCP server listed in the public MCP registry as io.github.SuperAngryMonkey/iris. Microsoft 365 mail MCP: drafts into Outlook; sending off by default, opt-in via IRIS_ENABLE_SEND. This page covers its PyPI package (iris-mcp).
Is the io.github.SuperAngryMonkey/iris MCP server safe to use?
io.github.SuperAngryMonkey/iris scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.SuperAngryMonkey/iris MCP server expose?
io.github.SuperAngryMonkey/iris exposes 8 tools: iris_login, iris_login_finish, iris_auth_status, iris_create_draft, iris_list_drafts, and 3 more. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Is the io.github.SuperAngryMonkey/iris MCP server still maintained?
io.github.SuperAngryMonkey/iris 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.