Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Outlook Calendar

NPM · @PIPEWORX/MCP-OUTLOOK-CALENDAR · 2 COMPONENTS

Outlook Calendar MCP Pack

85 Trust /100

Last scanned (1 day ago)

Scores higher than 87% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-outlook-calendar). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 466 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 4 Nov 26 +1
    • Package version: 0.2.0 → 0.2.1 functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 82

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-outlook-calendar@0.2.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 pipeworx-io/mcp-outlook-calendar
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-outlook-calendar/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3685210961
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:dd23f95ada32955799f2e4efee33cbec4003c62649f69db26b1408bad587fd9abb6ae3954173f63b80befa5643d6423c79185210810f0a37cff779cb5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~413 tokens

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 →

Tool Tokens
find_meeting_times ~92

Return the user's busy time windows from their Outlook / Microsoft 365 calendar over the next N days — a lightweight free/busy view. Each window includes start, end, subject, and all-day flag. Use to find when the user is available or to identify scheduling conflicts before proposing a meeting time.

NameTypeReqDescription
days_aheadnumber–How many days ahead to scan for busy windows (default 7).

No output schema declared.

No examples provided.

get_event ~73

Get full details of a single Outlook / Microsoft 365 calendar event by its ID. Returns subject, start/end times, location, organizer, attendees, body, all-day flag, and online meeting URL. Use after list_events to inspect a specific meeting.

NameTypeReqDescription
idstringyesThe Microsoft Graph event ID to retrieve.

No output schema declared.

No examples provided.

get_profile ~41

Get the signed-in user's Microsoft 365 / Outlook profile: display name, primary email (mail), and user principal name. Use to confirm whose calendar is connected.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_calendars ~52

List all calendars accessible in the user's Outlook / Microsoft 365 account. Returns each calendar's ID, name, owner, edit permission, and whether it is the default calendar. Use to discover which calendars exist.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_events ~155

List upcoming events from the user's Outlook / Microsoft 365 calendar within a time window. Returns subject, start/end times, location, organizer, all-day flag, and online meeting URL for each event. Defaults to the next 7 days. Use to see what meetings or appointments are scheduled.

NameTypeReqDescription
endstring–End of the window as an ISO 8601 datetime. Defaults to 7 days from now.
startstring–Start of the window as an ISO 8601 datetime (e.g., "2026-06-02T00:00:00Z"). Defaults to the current time.
topnumber–Maximum number of events to return (default 50, max 100).

No output schema declared.

No examples provided.

Install

How do I install the Outlook Calendar MCP server?

Outlook Calendar runs locally as an npm package, launched with npx -y @pipeworx/mcp-outlook-calendar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-outlook-calendar

# add to Claude Code
claude mcp add pipeworx-io-outlook-calendar -- npx -y @pipeworx/mcp-outlook-calendar
Common questions

What is the Outlook Calendar MCP server?

Outlook Calendar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/outlook-calendar. Outlook Calendar MCP Pack. This page covers its npm package (@pipeworx/mcp-outlook-calendar).

Is the Outlook Calendar MCP server safe to use?

Outlook Calendar scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 Outlook Calendar MCP server expose?

Outlook Calendar exposes 5 tools: list_events, get_event, list_calendars, find_meeting_times, get_profile. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.

Is the Outlook Calendar MCP server still maintained?

Outlook Calendar is still listed as active in the MCP registry. We last reached this channel on 4 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 Outlook Calendar MCP server under?

Outlook Calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.