io.github.robertdoneill/jmap-calendar-mcp
PYPI · JMAP-CALENDAR-MCP
Read calendars and create, change or (opt-in) delete events on any JMAP server, such as Stalwart.
Available components
Last scanned (1 day ago)
Scores higher than 64% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 489 tokens (~122/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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 Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 53
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 4 Nov 2026 · Analysed pypi/jmap-calendar-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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_calendar_event ~191
Create an event. Confirm title, time and time zone with the user first. Attendees are added without being emailed unless send_invitations is true.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | – | – |
| attendees | array | – | Email addresses |
| calendar | string | – | Calendar name or id; default calendar if omitted |
| days | integer | – | Length of an all-day event, default 1 |
| description | string | – | – |
| duration_minutes | integer | – | Default 60 |
| location | string | – | – |
| send_invitations | boolean | – | Email invitations to attendees. Only when the user asked for it. |
| start | string | yes | Local start time, YYYY-MM-DDTHH:MM (a date alone for all-day) |
| time_zone | string | – | IANA zone for a timed event, e.g. America/Chicago |
| title | string | yes | – |
No output schema declared.
No examples provided.
find_calendar_events ~91
Find events between two times (default: the next 30 days), optionally matching text. Recurring events are expanded into their occurrences.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | ISO date/time; UTC unless an offset is given |
| before | string | – | ISO date/time; UTC unless an offset is given |
| calendar | string | – | – |
| limit | integer | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
list_calendars ~24
List the calendars this account can see, with which is the default.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_calendar_event ~183
Change an existing event: give event_id and only the fields to change.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | – | – |
| attendees | array | – | Email addresses |
| calendar | string | – | Calendar name or id; default calendar if omitted |
| days | integer | – | Length of an all-day event, default 1 |
| description | string | – | – |
| duration_minutes | integer | – | Default 60 |
| event_id | string | yes | – |
| location | string | – | – |
| send_invitations | boolean | – | Email invitations to attendees. Only when the user asked for it. |
| start | string | – | Local start time, YYYY-MM-DDTHH:MM (a date alone for all-day) |
| time_zone | string | – | IANA zone for a timed event, e.g. America/Chicago |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.robertdoneill/jmap-calendar-mcp server?
io.github.robertdoneill/jmap-calendar-mcp runs locally as a PyPI package, launched with uvx jmap-calendar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · jmap-calendar-mcp
claude mcp add robertdoneill-jmap-calendar-mcp -- uvx jmap-calendar-mcp
What is the io.github.robertdoneill/jmap-calendar-mcp server?
io.github.robertdoneill/jmap-calendar-mcp is listed in the public MCP registry as io.github.robertdoneill/jmap-calendar-mcp. Read calendars and create, change or (opt-in) delete events on any JMAP server, such as Stalwart. This page covers its PyPI package (jmap-calendar-mcp).
Is the io.github.robertdoneill/jmap-calendar-mcp server safe to use?
io.github.robertdoneill/jmap-calendar-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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.robertdoneill/jmap-calendar-mcp server expose?
io.github.robertdoneill/jmap-calendar-mcp exposes 4 tools: list_calendars, find_calendar_events, create_calendar_event, update_calendar_event. Their descriptions and schemas cost roughly 489 tokens of context every time the server is loaded.
Is the io.github.robertdoneill/jmap-calendar-mcp server still maintained?
io.github.robertdoneill/jmap-calendar-mcp 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 io.github.robertdoneill/jmap-calendar-mcp server under?
io.github.robertdoneill/jmap-calendar-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.