Daylite Claude Connector (wimwoeber/daylite-claude-connector) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 29 tools. No publisher has claimed this listing.

D
Caution
58/100

Daylite Claude Connector

Connects Daylite CRM to Claude Code via the CalDAV interface to manage tasks and appointments. It enables users to list, create, update, and delete calendar events and to-dos directly through natural language.

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

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

wimwoeber

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: DAYLITE_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes29 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

daylite_list_appointments

Liste Termine aus Daylite auf. Optional filterbar nach Zeitraum.

daylite_get_appointment

Rufe einen einzelnen Daylite-Termin per ID ab.

daylite_create_appointment

Erstelle einen neuen Termin in Daylite.

daylite_update_appointment

Aktualisiere einen bestehenden Daylite-Termin.

daylite_delete_appointment

Lösche einen Termin aus Daylite.

daylite_list_companies

Firmen aus Daylite auflisten (REST API)

daylite_get_company

Eine bestimmte Firma aus Daylite abrufen

daylite_create_company

Neue Firma in Daylite anlegen

daylite_update_company

Bestehende Firma in Daylite aktualisieren

daylite_list_contacts

Kontakte aus Daylite auflisten (REST API)

daylite_get_contact

Einen bestimmten Kontakt aus Daylite abrufen

daylite_create_contact

Neuen Kontakt in Daylite anlegen

daylite_update_contact

Bestehenden Kontakt in Daylite aktualisieren

daylite_list_opportunities

Verkaufschancen (Opportunities) aus Daylite auflisten

daylite_get_opportunity

Eine bestimmte Verkaufschance aus Daylite abrufen

daylite_create_opportunity

Neue Verkaufschance in Daylite anlegen

daylite_update_opportunity

Bestehende Verkaufschance aktualisieren

daylite_list_projects

Projekte aus Daylite auflisten

daylite_get_project

Ein bestimmtes Projekt aus Daylite abrufen

daylite_create_project

Neues Projekt in Daylite anlegen

daylite_update_project

Bestehendes Projekt aktualisieren

daylite_search

Übergreifend in Daylite suchen (Kontakte, Firmen, Opportunities, Projekte)

daylite_list_pipelines

Verfügbare Pipelines aus Daylite auflisten

daylite_debug_raw

Debug: Zeigt die rohe API-Antwort für einen Endpoint (für Troubleshooting)

daylite_list_tasks

Liste alle Tasks/Aufgaben aus Daylite auf.

daylite_get_task

Rufe einen einzelnen Daylite-Task per URL ab.

daylite_create_task

Erstelle einen neuen Task in Daylite.

daylite_update_task

Aktualisiere einen bestehenden Daylite-Task.

daylite_delete_task

Lösche einen Task aus Daylite.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretDAYLITE_REFRESH_TOKEN"": "dein-refresh-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

29/29 tools missing one or more hints — daylite_list_appointments (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); daylite_get_appointment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); daylite_create_appointment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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

28/29 tool handlers declare input schemas (97%)

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

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (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.

// 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 6 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 Verified](https://m8ven.ai/badge/mcp/wimwoeber/daylite-claude-connector?variant=verified)](https://m8ven.ai/mcp/wimwoeber/daylite-claude-connector)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e7530ab3dcacaa82cbd8a3cd0c2e9894b1709ff3
code hash: 078013df54bc0cea408bfb8c4156559221b3f85f9a3b573f11bbeb4897c47335
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