Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google Calendar MCP

NPM · @RENZO.JOHNSON/GOOGLE-CALENDAR-MCP

Google Calendar MCP server: list, read, create, update and delete events and calendars.

+3 this week 67 Trust /100

Last scanned (21 hours ago)

Scores higher than 38% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

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 & Transparency19
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 256 tokens (~64/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 Management27
  • Stability observed for 8 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 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +3
    • Stability: unverified → 0.23 ▲ functional
  • 13 Nov 26 64

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@renzo.johnson/google-calendar-mcp@26.11.14

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~256 tokens

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 →

Tool Tokens
calendar_admin ~103

Google Calendar administration. Actions: create_event(summary, start_time, end_time, description?, location?, attendees?, calendar_id?, time_zone?), update_event(event_id, summary?, start_time?, end_time?, description?, location?, calendar_id?), list_calendars(), create_calendar(summary, description?, time_zone?). Destructive (confirm:true): delete_event(event_id, calendar_id?).

NameTypeReqDescription
actionstringyesAdmin action
paramsobject–Action parameters

No output schema declared.

No examples provided.

calendar_get_event ~45

Gets full details of a single calendar event by ID.

NameTypeReqDescription
calendar_idstring–Calendar ID (default: primary)
event_idstringyesCalendar event ID

No output schema declared.

No examples provided.

calendar_list_events ~94

Lists upcoming calendar events with attendees, location, and times.

NameTypeReqDescription
calendar_idstring–Calendar ID (default: primary)
max_resultsnumber–Max events (default 25)
querystring–Free-text search query
time_maxstring–End time in ISO 8601
time_minstring–Start time in ISO 8601 (default: now)

No output schema declared.

No examples provided.

ping ~14

Checks server connectivity and auth status

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Google Calendar MCP server?

Google Calendar MCP runs locally as an npm package, launched with npx -y @renzo.johnson/google-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.

npm · @renzo.johnson/google-calendar-mcp

# add to Claude Code
claude mcp add com-renzojohnson-google-calendar-mcp -- npx -y @renzo.johnson/google-calendar-mcp
Common questions

What is the Google Calendar MCP server?

Google Calendar MCP is listed in the public MCP registry as com.renzojohnson/google-calendar-mcp. Google Calendar MCP server: list, read, create, update and delete events and calendars. This page covers its npm package (@renzo.johnson/google-calendar-mcp).

Is the Google Calendar MCP server safe to use?

Google Calendar MCP scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Google Calendar MCP server expose?

Google Calendar MCP exposes 4 tools: ping, calendar_list_events, calendar_get_event, calendar_admin. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.

Is the Google Calendar MCP server still maintained?

Google Calendar MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 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.

What did VerifyMCP test on the Google Calendar MCP server?

VerifyMCP ran 15 checks on Google Calendar MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Google Calendar MCP: Security disclosure. 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.