Google_calendar
NPM · @PIPEWORX/MCP-GOOGLE_CALENDAR · 2 COMPONENTS
Google Calendar MCP Pack
Available components
Last scanned (11 hours ago)
Scores higher than 76% 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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-google_calendar). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 662 tokens (~132/item across 5 items; 5 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 Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +26
- Known CVEs: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 2 Nov 26 −25
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: pass → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 80
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/@pipeworx/mcp-google_calendar@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-google_calendar |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-google_calendar/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637331800 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cf7f34e1db17f0610c627b6aa32971ad7f06a89b425e7944ade8a1c1288854332b69318f184eccbb54dd94aa637876ceb2f79f7a5e60093ecf8c1a64f |
Background: How many MCP packages publish verified provenance →
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 →
gcal_create_event ~195
Create a new calendar event with summary, start/end times, optional description, location, and attendee emails. Returns the created event ID.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | List of attendee email addresses |
| calendar_id | string | – | Calendar ID (default: "primary") |
| description | string | – | Description or notes for the event |
| end | string | yes | End time as RFC3339 timestamp or date for all-day events |
| location | string | – | Location of the event |
| start | string | yes | Start time as RFC3339 timestamp (e.g., "2024-06-15T10:00:00-07:00") or date for all-day events ("2024-06-15") |
| summary | string | yes | Title of the event |
| time_zone | string | – | Time zone (e.g., "America/Los_Angeles"). Defaults to calendar's time zone. |
No output schema declared.
No examples provided.
gcal_get_event ~75
Get full details of a specific event by ID (e.g., "event_12345"). Returns summary, description, times, attendees, location, and video conferencing links.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | Calendar ID (default: "primary") |
| event_id | string | yes | The ID of the event to retrieve |
No output schema declared.
No examples provided.
gcal_list_calendars ~43
List all accessible calendars. Returns calendar IDs, names, time zones, and your access level for each. Use to identify which calendar to query or modify.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gcal_list_events ~166
List calendar events with optional date filtering. Returns event summaries, start/end times, attendees, and locations. Use to view upcoming or past events.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | Calendar ID (default: "primary" for the user's main calendar) |
| max_results | number | – | Maximum number of events to return (default 10, max 250) |
| order_by | string | – | Sort order (default: startTime). startTime requires singleEvents=true. |
| time_max | string | – | Upper bound (exclusive) for event end time as RFC3339 timestamp |
| time_min | string | – | Lower bound (inclusive) for event start time as RFC3339 timestamp (e.g., "2024-01-01T00:00:00Z") |
No output schema declared.
No examples provided.
gcal_search_events ~131
Search events by keyword across summaries, descriptions, locations, and attendees. Returns matching event details and times. Use to find events by topic or participant.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | string | – | Calendar ID (default: "primary") |
| max_results | number | – | Maximum number of events to return (default 10, max 250) |
| query | string | yes | Free-text search query to match against event fields |
| time_max | string | – | Upper bound for event end time as RFC3339 timestamp |
| time_min | string | – | Lower bound for event start time as RFC3339 timestamp |
No output schema declared.
No examples provided.
How do I install the Google_calendar MCP server?
Google_calendar runs locally as an npm package, launched with npx -y @pipeworx/mcp-google_calendar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-google_calendar
claude mcp add pipeworx-io-google-calendar -- npx -y @pipeworx/mcp-google_calendar
What is the Google_calendar MCP server?
Google_calendar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/google_calendar. Google Calendar MCP Pack. This page covers its npm package (@pipeworx/mcp-google_calendar).
Is the Google_calendar MCP server safe to use?
Google_calendar scores 83 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. Its build provenance is signed and verified. 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 Google_calendar MCP server expose?
Google_calendar exposes 5 tools: gcal_list_events, gcal_get_event, gcal_create_event, gcal_list_calendars, gcal_search_events. Their descriptions and schemas cost roughly 610 tokens of context every time the server is loaded.
Is the Google_calendar MCP server still maintained?
Google_calendar 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 Google_calendar MCP server under?
Google_calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.