Google Calendar MCP Server (naotaka3/google-calendar-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.
Enables Claude to interact with Google Calendar through natural language, providing the ability to view, create, update, and delete calendar events with persistent OAuth2 authentication.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
naotaka3
Source: Glama
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 →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
express vulnerable to XSS via response.redirect()
Express.js Open Redirect in malformed URLs
AUTH_HOSTAUTH_PORTYou can customize the authentication server port with "": "4153" (default is 4153)GOOGLE_CLIENT_IDyour_client_idGOOGLE_CLIENT_SECRETyour_client_secretGOOGLE_REDIRECT_URI"": "http://localhost:4153/oauth2callback"HOSTTOKEN_ENCRYPTION_KEY=your_64_character_hex_stringUSE_MANUAL_AUTHIf you're running in an environment where localhost is not accessible (e.g., remote server or container), add "": "true" to enable manual code entryPORTTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
10/10 tools missing one or more hints — getEvents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); createEvent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); updateEvent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.
Tool inputs are validated
Only 0/5 tool handlers declare input schemas (0%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Production dependencies are patched
0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.8.0 (high), @modelcontextprotocol/sdk@1.8.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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.
[](https://m8ven.ai/mcp/naotaka3-google-calendar-mcp-vz5pcv)?variant=verified from the URL.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