io.github.0xka13b/ms-calendar-mcp
NPM · MS-CALENDAR-MCP
Microsoft Calendar (Outlook Calendar) MCP server for managing events via Microsoft Graph.
Available components
Last scanned (2 hours ago)
Scores higher than 58% of npm servers
Category Productivity and Notes
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @azure/msal-node 5.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 40 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 149 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 620 tokens (~68/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 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.
- 25 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −6
- CVE-2026-109461 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.90 → pass security
- 15 Oct 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.
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 5 Nov 2026 · Analysed npm/ms-calendar-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-xcx6-jx8p-x3h5 | CVE-2026-109461 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 40 |
| 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 →
check_availability ~92
Check free/busy schedule for the current user and optional additional attendees within a time window.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | Additional attendee email addresses to check (current user is always included) |
| end | string | yes | End datetime in ISO 8601 format |
| start | string | yes | Start datetime in ISO 8601 format |
| timezone | string | – | Timezone for start/end. Defaults to UTC. |
No output schema declared.
No examples provided.
create_event ~173
Create a new calendar event.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | Attendee email addresses |
| body | string | – | Event description |
| body_type | string | – | Body content type. Defaults to text. |
| end | string | yes | End datetime in ISO 8601 format, e.g. '2024-01-15T11:00:00' |
| is_online_meeting | boolean | – | Create as an online meeting |
| location | string | – | Event location display name |
| start | string | yes | Start datetime in ISO 8601 format, e.g. '2024-01-15T10:00:00' |
| subject | string | yes | Event title |
| timezone | string | – | Timezone for start/end, e.g. 'America/New_York'. Defaults to UTC. |
No output schema declared.
No examples provided.
delete_event ~61
Delete a calendar event. If the user is the organizer, cancellation notices are sent to attendees.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event ID to delete |
| send_cancellation | boolean | – | Send cancellation email to attendees (organizer only). Defaults to true. |
No output schema declared.
No examples provided.
get_event ~26
Get a single calendar event by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event ID |
No output schema declared.
No examples provided.
list_events ~74
List calendar events within a date range. Recurring events are expanded.
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | integer | – | Days into the future. Defaults to 7. |
| days_back | integer | – | Days into the past. Defaults to 0. |
| include_details | boolean | – | Include event body and attendees. Defaults to true. |
No output schema declared.
No examples provided.
me ~21
Get the signed-in user's profile (id, displayName, mail).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
respond_event ~77
Accept, decline, or tentatively accept a calendar invitation.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event ID to respond to |
| message | string | – | Optional message to include with the response |
| response | string | – | Response type. Defaults to accept. |
| send_response | boolean | – | Send response email to organizer. Defaults to true. |
No output schema declared.
No examples provided.
search_events ~38
Search calendar events by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results. Defaults to 50. |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
update_event ~58
Update calendar event properties.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event ID to update |
| updates | object | yes | Properties to update, e.g. {"subject": "New Title", "location": {"displayName": "Room 1"}} |
No output schema declared.
No examples provided.
How do I install the io.github.0xka13b/ms-calendar-mcp server?
io.github.0xka13b/ms-calendar-mcp runs locally as an npm package, launched with npx -y ms-calendar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ms-calendar-mcp
claude mcp add 0xka13b-ms-calendar-mcp -- npx -y ms-calendar-mcp
What is the io.github.0xka13b/ms-calendar-mcp server?
io.github.0xka13b/ms-calendar-mcp is listed in the public MCP registry as io.github.0xka13b/ms-calendar-mcp. Microsoft Calendar (Outlook Calendar) MCP server for managing events via Microsoft Graph. This page covers its npm package (ms-calendar-mcp).
Is the io.github.0xka13b/ms-calendar-mcp server safe to use?
io.github.0xka13b/ms-calendar-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.0xka13b/ms-calendar-mcp server expose?
io.github.0xka13b/ms-calendar-mcp exposes 9 tools: me, list_events, get_event, create_event, update_event, and 4 more. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Is the io.github.0xka13b/ms-calendar-mcp server still maintained?
io.github.0xka13b/ms-calendar-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.0xka13b/ms-calendar-mcp server under?
io.github.0xka13b/ms-calendar-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.