io.github.CloudCorpRecords/calendarport
NPM · @RENETURCIOS/CALENDARPORT · 2 COMPONENTS
Google Calendar calendars, events and free-busy checks, as MCP tools.
Available components
Last scanned (10 hours ago)
Scores higher than 32% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 796 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_event" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 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.
- 4 Nov 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.
- 2 Nov 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.
- 1 Nov 26 63
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/@reneturcios/calendarport@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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
check_free_busy ~92
Check free-busy availability for one or more calendars over a time range.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_ids | array | yes | The IDs of the calendars to check free-busy availability for. |
| time_max | string | yes | The end of the time range to check, as an RFC 3339 timestamp. |
| time_min | string | yes | The start of the time range to check, as an RFC 3339 timestamp. |
No output schema declared.
No examples provided.
create_calendar ~31
Create a new Google Calendar calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| summary | string | yes | The title (summary) of the new calendar. |
No output schema declared.
No examples provided.
create_event ~150
Create a new event on a Google Calendar calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | The email addresses of the event attendees, each added as an attendee. |
| calendar_id | string | – | The ID of the calendar to create the event on. Defaults to "primary" if omitted. |
| description | string | – | A description of the event. |
| end | string | yes | The end time of the event, as an RFC 3339 date-time string. |
| location | string | – | The location of the event. |
| start | string | yes | The start time of the event, as an RFC 3339 date-time string. |
| summary | string | yes | The title (summary) of the new event. |
No output schema declared.
No examples provided.
delete_event ~58
Delete an event from a Google Calendar calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | The ID of the calendar to delete the event from. Defaults to "primary" if omitted. |
| event_id | string | yes | The ID of the event to delete. |
No output schema declared.
No examples provided.
get_calendar ~32
Get a Google Calendar calendar by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | yes | The ID of the calendar to retrieve. |
No output schema declared.
No examples provided.
get_event ~59
Get a single event from a Google Calendar calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | The ID of the calendar to get the event from. Defaults to "primary" if omitted. |
| event_id | string | yes | The ID of the event to retrieve. |
No output schema declared.
No examples provided.
list_calendars ~21
List the calendars in the user's Google Calendar calendar list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_events ~129
List events on a Google Calendar calendar, optionally within a time range.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | The ID of the calendar to list events from. Defaults to "primary" if omitted. |
| max_results | number | – | The maximum number of events to return. |
| query | string | – | Free-text search query to filter events by. |
| time_max | string | – | The end of the time range to list events in, as an RFC 3339 timestamp. |
| time_min | string | – | The start of the time range to list events in, as an RFC 3339 timestamp. |
No output schema declared.
No examples provided.
quick_add_event ~73
Create an event on a Google Calendar calendar from a free-text description.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | The ID of the calendar to create the event on. Defaults to "primary" if omitted. |
| text | string | yes | The free-text description of the event to create, parsed by Google Calendar into an event. |
No output schema declared.
No examples provided.
update_event ~151
Update fields of an existing event on a Google Calendar calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | The ID of the calendar to update the event on. Defaults to "primary" if omitted. |
| description | string | – | The new description of the event. |
| end | string | – | The new end time of the event, as an RFC 3339 date-time string. |
| event_id | string | yes | The ID of the event to update. |
| location | string | – | The new location of the event. |
| start | string | – | The new start time of the event, as an RFC 3339 date-time string. |
| summary | string | – | The new title (summary) of the event. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/calendarport MCP server?
io.github.CloudCorpRecords/calendarport runs locally as an npm package, launched with npx -y @reneturcios/calendarport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/calendarport
claude mcp add cloudcorprecords-calendarport -- npx -y @reneturcios/calendarport
What is the io.github.CloudCorpRecords/calendarport MCP server?
io.github.CloudCorpRecords/calendarport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/calendarport. Google Calendar calendars, events and free-busy checks, as MCP tools. This page covers its npm package (@reneturcios/calendarport).
Is the io.github.CloudCorpRecords/calendarport MCP server safe to use?
io.github.CloudCorpRecords/calendarport scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.CloudCorpRecords/calendarport MCP server expose?
io.github.CloudCorpRecords/calendarport exposes 10 tools: list_calendars, get_calendar, create_calendar, list_events, get_event, and 5 more. Their descriptions and schemas cost roughly 796 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/calendarport MCP server still maintained?
io.github.CloudCorpRecords/calendarport 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.CloudCorpRecords/calendarport MCP server under?
io.github.CloudCorpRecords/calendarport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.