Calendar MCP Servers: 9 Implementations Compared

The MCP ecosystem often has several independent packages implementing the same tool — and "Calendar" currently has 9. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.

ImplementationPackageTrustCapabilityCoverageFindingsScanned
Calendarbest by PyPI calendar PyPI A 100/100 Minimal Metadata 0 2026-07-22
Calendar by Masbuc53 calendar-mcp npm A 100/100 Minimal Source 0 2026-07-22
Calendar by nchufa @nchufa/calendar npm A 100/100 Minimal Source 0 2026-07-22
Calendar by shirabe-api @shirabe-api/calendar-mcp npm A 100/100 Minimal Metadata 0 2026-07-22
Calendar by gongrzhe @gongrzhe/server-calendar-mcp npm A 100/100 Minimal Source 0 2026-07-22
Calendar by franciscpd @franciscpd/calendar-mcp-server npm A 100/100 Minimal Source 0 2026-07-22
Google Calendar (Infoinlet) by infoinlet @infoinlet/mcp-calendar npm A 98/100 Minimal Source 1 2026-07-22
Calendar by p-w-4-z calendar-mcp PyPI A 98/100 Minimal Source 1 2026-07-22
Calendar Source verified by antidrift @antidrift/mcp-calendar npm A 94/100 High Source 3 2026-07-22

A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.