YDrogen/calendar-mcp (YDrogen/calendar-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 28 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

YDrogen/calendar-mcp

Enables MCP clients to manage Google Calendar events, including CRUD operations, recurring events, free/busy queries, and push notifications via webhooks.

→ YDrogen/calendar-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

YDrogen

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 2 credentials: CALENDAR_MCP_ENCRYPTION_KEY, GOOGLE_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretCALENDAR_MCP_ENCRYPTION_KEYNo auto-generated 64-character hex string for AES-256-GCM token encryption
configGOOGLE_CLIENT_IDYes — Google OAuth2 client ID
🔐 secretGOOGLE_CLIENT_SECRETYes — Google OAuth2 client secret
configHTTP_PORTNo 3000 HTTP server port for SSE and webhook endpoints
configMCP_ALLOWED_HOSTSNo — Comma-separated allowed hosts for HTTP transport (DNS rebinding protection). When unset, all hosts are allowed
configOAUTH_PORT6. Add http://localhost:3500/oauth2callback as an authorized redirect URI (or use your configured )
// quality suggestions

Tool annotations

17/28 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

28/28 tools missing one or more hints — list_events (missing: destructiveHint, idempotentHint, openWorldHint); get_event (missing: destructiveHint, idempotentHint, openWorldHint); create_event (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Domain consistency

npm scope @calendar-mcp doesn't match GitHub owner ydrogen

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ydrogen/calendar-mcp)](https://m8ven.ai/mcp/ydrogen/calendar-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2fff2c7e0701c39354db6d71e5a732b07bae94e4
code hash: b01c2e9d41f7fc39d37943c2be7f1770dadb974d3c4b0cf7dee95f0a56c8a043
verified: 8/7/2026, 2:20:57 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client