# io.github.CloudCorpRecords/calendarport (npm · @reneturcios/calendarport)

Google Calendar calendars, events and free-busy checks, as MCP tools.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/calendarport`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport.md), [page](https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport)
- oci · `ghcr.io/cloudcorprecords/calendarport`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-calendarport/ghcr-io-cloudcorprecords-calendarport.md), [page](https://verifymcp.io/servers/cloudcorprecords-calendarport/ghcr-io-cloudcorprecords-calendarport)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/calendarport`
- 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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 796 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 10 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.CloudCorpRecords/calendarport MCP server?

io.github.CloudCorpRecords/calendarport runs locally as an npm package, launched with npx -y @reneturcios/calendarport 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 cloudcorprecords-calendarport -- npx -y @reneturcios/calendarport mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-calendarport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/calendarport",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-calendarport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/calendarport",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-calendarport -- npx -y @reneturcios/calendarport mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-calendarport": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/calendarport",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-calendarport --command npx --arg -y --arg @reneturcios/calendarport --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-calendarport:
    command: "npx"
    args: ["-y", "@reneturcios/calendarport", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-calendarport": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/calendarport",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-calendarport -t stdio -c npx -a -y @reneturcios/calendarport mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-calendarport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/calendarport",
        "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-04 (score 65, +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-11-02 (score 64, +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-11-01 (score 63)

First indexed and scored.

## MCP tools (10)

### `list_calendars` (~21 tokens)

List the calendars in the user's Google Calendar calendar list.

### `get_calendar` (~32 tokens)

Get a Google Calendar calendar by its ID.

Input parameters:

- `calendar_id` (string, required): The ID of the calendar to retrieve.

### `create_calendar` (~31 tokens)

Create a new Google Calendar calendar.

Input parameters:

- `summary` (string, required): The title (summary) of the new calendar.

### `list_events` (~129 tokens)

List events on a Google Calendar calendar, optionally within a time range.

Input parameters:

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

### `get_event` (~59 tokens)

Get a single event from a Google Calendar calendar.

Input parameters:

- `calendar_id` (string): The ID of the calendar to get the event from. Defaults to "primary" if omitted.
- `event_id` (string, required): The ID of the event to retrieve.

### `create_event` (~150 tokens)

Create a new event on a Google Calendar calendar.

Input parameters:

- `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, required): The end time of the event, as an RFC 3339 date-time string.
- `location` (string): The location of the event.
- `start` (string, required): The start time of the event, as an RFC 3339 date-time string.
- `summary` (string, required): The title (summary) of the new event.

### `update_event` (~151 tokens)

Update fields of an existing event on a Google Calendar calendar.

Input parameters:

- `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, required): 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.

### `delete_event` (~58 tokens)

Delete an event from a Google Calendar calendar.

Input parameters:

- `calendar_id` (string): The ID of the calendar to delete the event from. Defaults to "primary" if omitted.
- `event_id` (string, required): The ID of the event to delete.

### `quick_add_event` (~73 tokens)

Create an event on a Google Calendar calendar from a free-text description.

Input parameters:

- `calendar_id` (string): The ID of the calendar to create the event on. Defaults to "primary" if omitted.
- `text` (string, required): The free-text description of the event to create, parsed by Google Calendar into an event.

### `check_free_busy` (~92 tokens)

Check free-busy availability for one or more calendars over a time range.

Input parameters:

- `calendar_ids` (array, required): The IDs of the calendars to check free-busy availability for.
- `time_max` (string, required): The end of the time range to check, as an RFC 3339 timestamp.
- `time_min` (string, required): The start of the time range to check, as an RFC 3339 timestamp.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63

## Common questions

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/calendarport MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/calendarport, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/calendarport
- Socket report: https://socket.dev/npm/package/@reneturcios/calendarport
- Repository: https://github.com/CloudCorpRecords/calendarport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-calendarport/reneturcios-calendarport