io.github.da-the-dev/pim-mcp
NPM · PIM-MCP
Local MCP server for your calendars across Nextcloud, iCloud, Google and any CalDAV server.
Available components
Last scanned (9 hours ago)
Scores higher than 42% 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 Security98
- 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
- 31 of 97 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 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 25 Oct 26 66
First indexed and scored.
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/pim-mcp@0.1.0
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 →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
create_event ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM) |
| title | string | yes | – |
No output schema declared.
No examples provided.
delete_event ~65
Delete an event. For recurring events pass `scope` ("instance" removes one occurrence, "series" removes all).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| scope | string | – | Required for recurring events: "instance" = only this occurrence, "series" = every occurrence. |
No output schema declared.
No examples provided.
find_free_time ~159
Free time windows of at least `duration_minutes` across all (or selected) calendars. Events marked free/transparent and cancelled events do not block time.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | – | – |
| calendars | array | – | – |
| duration_minutes | integer | yes | – |
| end | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
get_event ~30
Full details of one event (description, attendees, organizer, recurrence rule).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_calendars ~35
List every calendar across all configured accounts (Nextcloud, iCloud, Google, …), with ids usable in other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_events ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
search_events ~124
Find events whose title, location or description contains the query (case-insensitive). Defaults to 90 days back through 365 days ahead.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| start | string | – | YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM (local to the configured timezone unless it has Z/±HH:MM) |
No output schema declared.
No examples provided.
update_event ~266
Change an event. Only the fields you pass change; moving `start` alone keeps the duration. For recurring events pass `scope`.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
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.
npm · pim-mcp
claude mcp add da-the-dev-pim-mcp -- npx -y pim-mcp
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.