# Apple Calendar (mcpb · apple-calendar-mcp-0.3.0.mcpb)

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

- Trust score: 57/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `apple-calendar-mcp-0.3.0.mcpb`: 57/100 (this document), [markdown](https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp.md), [page](https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp)
- npm · `@redpop/apple-calendar-mcp`: 49/100, [markdown](https://verifymcp.io/servers/redpop-apple-calendar-mcp/redpop-apple-calendar-mcp.md), [page](https://verifymcp.io/servers/redpop-apple-calendar-mcp/redpop-apple-calendar-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/redpop/apple-calendar-mcp/releases/download/v0.3.0/apple-calendar-mcp-0.3.0.mcpb`
- Version: `0.3.0`
- Transport: `stdio`
- SHA-256: `4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 25/100
  - 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.
  - Known CVEs were checked across the 3 of 3 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to redpop/apple-calendar-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

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

- Download bundle: `https://github.com/redpop/apple-calendar-mcp/releases/download/v0.3.0/apple-calendar-mcp-0.3.0.mcpb`
- SHA-256: `4c6b24c1d2762a130a04d4b5c57e3f8f2a109f7a440ee4254d8561ef0a4e9801`

### Verify on macOS / Linux

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

### Verify on Windows (PowerShell)

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-12 (score 57)

First indexed and scored.

## MCP tools (6)

### `list_calendars` (~51 tokens)

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.

### `list_events` (~147 tokens)

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.

Input parameters:

- `calendarIds` (array): Restrict to these calendars. Defaults to all of them.
- `end` (string, required): End of the range, ISO 8601 with offset
- `maxResults` (integer): Maximum number of events to return
- `query` (string): Free-text filter applied to titles and notes
- `start` (string, required): Start of the range, ISO 8601 with offset

### `create_event` (~288 tokens)

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.

Input parameters:

- `alarmMinutesBefore` (array): Alarms in minutes before the start. For all-day events these are floored to whole days and placed at 09:00, matching Calendar.app.
- `allDay` (boolean): All-day event. When true, only the calendar days of start and end are used.
- `calendarId` (string): Calendar to create the event in. Defaults to the system default calendar.
- `end` (string, required): End, 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 (…
- `location` (string): Location, as shown in Calendar.app
- `notes` (string): Free-text note attached to the event
- `start` (string, required): Start, ISO 8601 with offset
- `title` (string, required): Title of the event
- `url` (string): Associated URL, for example a meeting link

### `update_event` (~314 tokens)

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.

Input parameters:

- `alarmMinutesBefore` (array): Replaces all existing alarms. Pass an empty array to remove them.
- `allDay` (boolean): Turn the event into an all-day event, or back
- `end` (string): New end, ISO 8601 with offset
- `eventIdentifier` (string, required): Identifier of the event, from list_events. For a recurring event this names the series, not one occurrence.
- `location` (string): New location
- `notes` (string): New notes, replacing the previous ones
- `occurrenceDate` (string): The occurrenceDate of the specific instance, exactly as returned by list_events. Required for recurring events.
- `span` (string): 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…
- `start` (string): New start, ISO 8601 with offset
- `title` (string): New title
- `url` (string): New associated URL. An empty string removes it.

### `delete_event` (~191 tokens)

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.

Input parameters:

- `eventIdentifier` (string, required): Identifier of the event, from list_events. For a recurring event this names the series, not one occurrence.
- `occurrenceDate` (string): The occurrenceDate of the specific instance, exactly as returned by list_events. Required for recurring events.
- `span` (string): 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…

### `find_free_time` (~279 tokens)

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.

Input parameters:

- `activityDomain` (string): work: Mon-Fri 09:00-18:00. personal: every day 09:00-18:00. unrestricted: every day, around the clock.
- `bufferMinutes` (integer): 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.
- `calendarIds` (array): Treat these calendars as busy. Defaults to all of them.
- `durationMinutes` (integer, required): Required duration in minutes
- `end` (string, required): End of the search window
- `ignoreAllDay` (boolean): All-day events do not count as busy
- `start` (string, required): Start of the search window
- `workingHours` (object): Overrides only the hours of the activityDomain, not which days it covers

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp#diagnostics

## Score history

- 2026-11-21: 57
- 2026-11-20: 57
- 2026-11-19: 57
- 2026-11-18: 57
- 2026-11-17: 57
- 2026-11-16: 57
- 2026-11-15: 57
- 2026-11-14: 57
- 2026-11-13: 57
- 2026-11-12: 57

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

## Links

- Repository: https://github.com/redpop/apple-calendar-mcp
- Changelog RSS feed: https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/redpop-apple-calendar-mcp/apple-calendar-mcp
