# io.github.da-the-dev/pim-mcp (npm · pim-mcp)

Local MCP server for your calendars across Nextcloud, iCloud, Google and any CalDAV server.

- Trust score: 72/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `pim-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/da-the-dev-pim-mcp/pim-mcp.md), [page](https://verifymcp.io/servers/da-the-dev-pim-mcp/pim-mcp)

## Channel facts

- Registry: `npm`
- Package: `pim-mcp`
- Version: `0.1.0`
- Transport: `stdio`

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

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1198 tokens (~149/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% 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 9 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.

## Install

### How do I install the io.github.da-the-dev/pim-mcp server?

io.github.da-the-dev/pim-mcp runs locally as an npm package, launched with npx -y pim-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add da-the-dev-pim-mcp -- npx -y pim-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "da-the-dev-pim-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pim-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "da-the-dev-pim-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pim-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add da-the-dev-pim-mcp -- npx -y pim-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "da-the-dev-pim-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pim-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add da-the-dev-pim-mcp --command npx --arg -y --arg pim-mcp
```

### Hermes

```yaml
mcp_servers:
  da-the-dev-pim-mcp:
    command: "npx"
    args: ["-y", "pim-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "da-the-dev-pim-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pim-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add da-the-dev-pim-mcp -t stdio -c npx -a -y pim-mcp
```

### Other

```json
{
  "mcpServers": {
    "da-the-dev-pim-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pim-mcp"
      ]
    }
  }
}
```

## 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-05 (score 72, +1)

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

### 2026-11-03 (score 71, +1)

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

### 2026-11-01 (score 70, +1)

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

### 2026-10-30 (score 69, +1)

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

### 2026-10-28 (score 68, +1)

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

### 2026-10-26 (score 67, +1)

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

### 2026-10-25 (score 66)

First indexed and scored.

## MCP tools (8)

### `list_calendars` (~35 tokens)

List every calendar across all configured accounts (Nextcloud, iCloud, Google, …), with ids usable in other tools.

### `list_events` (~158 tokens)

Events in a time range, merged across all calendars and sorted by start. Recurring events are expanded into occurrences. Defaults to today through the next 7 days.

Input parameters:

- `accounts` (array): Account ids to limit to (default: all).
- `calendars` (array): Calendar ids or names to limit to (default: all).
- `end` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM). A date-only end includes that whole day.
- `start` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)

### `search_events` (~124 tokens)

Find events whose title, location or description contains the query (case-insensitive). Defaults to 90 days back through 365 days ahead.

Input parameters:

- `calendars` (array)
- `end` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)
- `query` (string, required)
- `start` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)

### `get_event` (~30 tokens)

Full details of one event (description, attendees, organizer, recurrence rule).

Input parameters:

- `id` (string, required)

### `find_free_time` (~159 tokens)

Free time windows of at least `duration_minutes` across all (or selected) calendars. Events marked free/transparent and cancelled events do not block time.

Input parameters:

- `accounts` (array)
- `calendars` (array)
- `duration_minutes` (integer, required)
- `end` (string, required): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM). A date-only end includes that whole day.
- `start` (string, required): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)
- `working_hours` (object): Only return time inside these hours.

### `create_event` (~259 tokens)

Create an event. `start` as a date makes an all-day event. Without `end`, timed events last 1 hour and all-day events 1 day.

Input parameters:

- `alarm_minutes`: Reminder N minutes before start; null removes reminders.
- `attendees` (array): Email addresses. The server may email invitations.
- `busy` (boolean): Whether the event blocks time (default: true for timed, false for all-day).
- `calendar` (string, required): Calendar id (from list_calendars) or exact name.
- `description` (string|null)
- `end` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM). For all-day events the end date is inclusive.
- `location` (string|null)
- `rrule` (string|null): iCalendar RRULE, e.g. "FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10". null removes recurrence.
- `start` (string, required): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)
- `title` (string, required)

### `update_event` (~266 tokens)

Change an event. Only the fields you pass change; moving `start` alone keeps the duration. For recurring events pass `scope`.

Input parameters:

- `alarm_minutes`: Reminder N minutes before start; null removes reminders.
- `attendees` (array): Email addresses. The server may email invitations.
- `busy` (boolean): Whether the event blocks time (default: true for timed, false for all-day).
- `description` (string|null)
- `end` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM). For all-day events the end date is inclusive.
- `id` (string, required)
- `location` (string|null)
- `rrule` (string|null): iCalendar RRULE, e.g. "FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10". null removes recurrence.
- `scope` (string): Required for recurring events: "instance" = only this occurrence, "series" = every occurrence.
- `start` (string): YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM)
- `title` (string)

### `delete_event` (~65 tokens)

Delete an event. For recurring events pass `scope` ("instance" removes one occurrence, "series" removes all).

Input parameters:

- `id` (string, required)
- `scope` (string): Required for recurring events: "instance" = only this occurrence, "series" = every occurrence.

## Diagnostics

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

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66

## Common questions

### What is the io.github.da-the-dev/pim-mcp server?

io.github.da-the-dev/pim-mcp is listed in the public MCP registry as io.github.da-the-dev/pim-mcp. Local MCP server for your calendars across Nextcloud, iCloud, Google and any CalDAV server. This page covers its npm package (pim-mcp).

### Is the io.github.da-the-dev/pim-mcp server safe to use?

io.github.da-the-dev/pim-mcp scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting 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.da-the-dev/pim-mcp server expose?

io.github.da-the-dev/pim-mcp exposes 8 tools: list_calendars, list_events, search_events, get_event, find_free_time, and 3 more. Their descriptions and schemas cost roughly 1,096 tokens of context every time the server is loaded.

### Is the io.github.da-the-dev/pim-mcp server still maintained?

io.github.da-the-dev/pim-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.da-the-dev/pim-mcp server under?

io.github.da-the-dev/pim-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.

## Links

- npm package: https://www.npmjs.com/package/pim-mcp
- Socket report: https://socket.dev/npm/package/pim-mcp
- Repository: https://github.com/da-the-dev/pim-mcp
- Changelog RSS feed: https://verifymcp.io/servers/da-the-dev-pim-mcp/pim-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/da-the-dev-pim-mcp/pim-mcp.json
- HTML version of this page: https://verifymcp.io/servers/da-the-dev-pim-mcp/pim-mcp