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.

Apple Calendar

MCPB · APPLE-CALENDAR-MCP-0.3.0.MCPB · 2 COMPONENTS

Read, create, update and delete Apple Calendar events on macOS, and find free time.

0 this week 57 Trust /100

Last scanned (17 hours ago)

Scores higher than 91% of MCPB 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 Security25
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs were checked across the 3 of 3 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to redpop/apple-calendar-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1371 tokens (~228/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 12 Nov 26 57

    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 21 Nov 2026 · Analysed mcpb/https://github.com/redpop/apple-calendar-mcp/releases/download/v0.3.0/apple-calendar-mcp-0.3.0.mcpb@0.3.0

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 mcpb
Reason Verified
Discovered via GitHub artifact attestations
Source repo redpop/apple-calendar-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/redpop/apple-calendar-mcp/.github/workflows/release.yml@refs/tags/v0.3.0
Rekor log index 3837052560
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,270 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
create_event ~288

Creates a new event. Without calendarId the default calendar is used. Read-only calendars are rejected. For all-day events, alarms are floored to whole days and placed at 09:00, matching Calendar.app. Never modifies or deletes existing events — neither is currently possible.

NameTypeReqDescription
alarmMinutesBeforearray–Alarms in minutes before the start. For all-day events these are floored to whole days and placed at 09:00, matching Calendar.app.
allDayboolean–All-day event. When true, only the calendar days of start and end are used.
calendarIdstring–Calendar to create the event in. Defaults to the system default calendar.
endstringyesEnd, ISO 8601 with offset. For all-day events (allDay: true) both common conventions are accepted and normalised to the same day: the last day included (…T23:59:59) or midnight of the following day (…
locationstring–Location, as shown in Calendar.app
notesstring–Free-text note attached to the event
startstringyesStart, ISO 8601 with offset
titlestringyesTitle of the event
urlstring–Associated URL, for example a meeting link

No output schema declared.

No examples provided.

delete_event ~191

Deletes an event. Get eventIdentifier from list_events. For a recurring event, also pass occurrenceDate to name the instance and span to say how far the deletion reaches — this removes only that occurrence, future removes it and every later one. There is no undo, and span is not optional for recurring events for that reason. Read-only calendars are rejected. Returns the event as it was before deletion.

NameTypeReqDescription
eventIdentifierstringyesIdentifier of the event, from list_events. For a recurring event this names the series, not one occurrence.
occurrenceDatestring–The occurrenceDate of the specific instance, exactly as returned by list_events. Required for recurring events.
spanstring–How far the change reaches on a recurring event. 'this' affects only the occurrence named by occurrenceDate; 'future' affects that occurrence and every later one. Required for recurring events, ignor…

No output schema declared.

No examples provided.

find_free_time ~279

Finds free slots of at least durationMinutes. activityDomain controls days and hours together: work means Mon-Fri 09:00-18:00, personal every day at the same hours, unrestricted every day around the clock. workingHours overrides only the hours. bufferMinutes keeps time free around each busy event, so a slot wedged between two meetings is not offered as usable. Returns the free gaps, not the busy events — use list_events for those. Creates nothing.

NameTypeReqDescription
activityDomainstring–work: Mon-Fri 09:00-18:00. personal: every day 09:00-18:00. unrestricted: every day, around the clock.
bufferMinutesinteger–Free time to keep before and after each busy event, in minutes. Use this when a slot pressed directly between two meetings would not actually be usable.
calendarIdsarray–Treat these calendars as busy. Defaults to all of them.
durationMinutesintegeryesRequired duration in minutes
endstringyesEnd of the search window
ignoreAllDayboolean–All-day events do not count as busy
startstringyesStart of the search window
workingHoursobject–Overrides only the hours of the activityDomain, not which days it covers

No output schema declared.

No examples provided.

list_calendars ~51

Lists every calendar configured in macOS Calendar, including iCloud ones. Returns id, title, type, source, color and allowsModifications for each. Does not read events — list_events does that.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_events ~147

Reads events in a date range. Recurring events are returned as individual occurrences. All-day events additionally carry startDay and endDay as plain dates, where endDay means the last day included. Changes nothing. For free gaps rather than busy events, use find_free_time.

NameTypeReqDescription
calendarIdsarray–Restrict to these calendars. Defaults to all of them.
endstringyesEnd of the range, ISO 8601 with offset
maxResultsinteger–Maximum number of events to return
querystring–Free-text filter applied to titles and notes
startstringyesStart of the range, ISO 8601 with offset

No output schema declared.

No examples provided.

update_event ~314

Changes an existing event. Only the fields you pass are changed; anything left out keeps its current value. Get eventIdentifier from list_events. For a recurring event, also pass occurrenceDate to name the instance and span to say how far the change reaches — this affects only that occurrence, future affects it and every later one. Read-only calendars are rejected. Alarms, if given, replace all existing ones.

NameTypeReqDescription
alarmMinutesBeforearray–Replaces all existing alarms. Pass an empty array to remove them.
allDayboolean–Turn the event into an all-day event, or back
endstring–New end, ISO 8601 with offset
eventIdentifierstringyesIdentifier of the event, from list_events. For a recurring event this names the series, not one occurrence.
locationstring–New location
notesstring–New notes, replacing the previous ones
occurrenceDatestring–The occurrenceDate of the specific instance, exactly as returned by list_events. Required for recurring events.
spanstring–How far the change reaches on a recurring event. 'this' affects only the occurrence named by occurrenceDate; 'future' affects that occurrence and every later one. Required for recurring events, ignor…
startstring–New start, ISO 8601 with offset
titlestring–New title
urlstring–New associated URL. An empty string removes it.

No output schema declared.

No examples provided.

Install

How do I install the Apple Calendar MCP server?

Apple Calendar ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801; the commands to do that are on this page. If it does not match, do not open it.

mcpb · apple-calendar-mcp-0.3.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801

macOS / Linux

echo "4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801  apple-calendar-mcp-0.3.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\apple-calendar-mcp-0.3.0.mcpb).Hash -eq "4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the Apple Calendar MCP server?

Apple Calendar is an MCP server listed in the public MCP registry as io.github.redpop/apple-calendar-mcp. Read, create, update and delete Apple Calendar events on macOS, and find free time. This page covers its MCPB bundle (https://github.com/redpop/apple-calendar-mcp/releases/download/v0.3.0/apple-calendar-mcp-0.3.0.mcpb).

Is the Apple Calendar MCP server safe to use?

Apple Calendar scores 57 out of 100 on VerifyMCP. 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 Apple Calendar MCP server expose?

Apple Calendar exposes 6 tools: list_calendars, list_events, create_event, update_event, delete_event, find_free_time. Their descriptions and schemas cost roughly 1,270 tokens of context every time the server is loaded.

What licence is the Apple Calendar MCP server under?

Apple 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.

What did VerifyMCP test on the Apple Calendar MCP server?

VerifyMCP ran 14 checks on Apple Calendar, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Apple Calendar: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.