Back to MCP Trust Indexm8ven
C
Emerging
74/100
1 day ago

caldav-mcp

An MCP server that gives AI assistants read/write access to any CalDAV calendar, enabling natural language management of events, attendees, and calendar queries across Nextcloud, Radicale, iCloud, and more.

→ gelse/caldav-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

gelse

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.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: CALDAV_PASSWORD, CALDAV_MCP_TLS_KEY, CALDAV_MCP_API_KEY
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.
configCALDAV_URL2. Environment variables (fallback): , CALDAV_USERNAME,
configCALDAV_USERNAME2. Environment variables (fallback): CALDAV_URL, ,
🔐 secretCALDAV_PASSWORDapp-password
configCALDAV_MCP_RATE_LIMIT_MAX_FAILURESwindow. Configurable via and
configCALDAV_MCP_RATE_LIMIT_WINDOW_SECONDS60 Sliding window duration in seconds
configCALDAV_MCP_TLS_CERTOption A: Enable built-in TLS by setting and
🔐 secretCALDAV_MCP_TLS_KEY. The server listens on HTTPS directly.
configCALDAV_MCP_TLS_CA_BUNDLE"" Optional CA bundle for custom certificate authorities
configCALDAV_MCP_CALDAV_VERIFY_SSLtrue Verify TLS certs on CalDAV connections. Set false only for testing with self-signed certs.
configCALDAV_MCP_LOG_FORMATjson for structured JSON output suitable for log
configCALDAV_MCP_PORT8080 Listen port (inside container)
configCALDAV_MCP_PATH/mcp Streamable HTTP endpoint path
🔐 secretCALDAV_MCP_API_KEYyour-secret-token
// quality suggestions

Tool 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

14/14 tools missing one or more hints — caldav_add_attendee (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); caldav_remove_attendee (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); caldav_list_attendees (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +11 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

13/14 tool handlers declare input schemas (93%)

Declare an inputSchema with zod/joi/yup on every tool definition.

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 3 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/gelse-caldav-mcp-p1nzjs)](https://m8ven.ai/mcp/gelse-caldav-mcp-p1nzjs)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b978997f59c7db45180b2e851f840b4270716a17
code hash: 927ab2a326791f7c5436f9a5e245d58dc03f44aff4339fba34136900a53c113b
verified: 8/21/2026, 9:04:58 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