caldav-mcp@0.1.5
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server for CalDAV calendars: events, tasks and journals over the open standard" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
CALDAV_PASSWORDCALDAV_TOKENConfiguration, not credentials: CALDAV_ALLOW_PLAINTEXT, CALDAV_ALLOW_TOOLS, CALDAV_CALENDARS, CALDAV_DENY_TOOLS, CALDAV_INSECURE_TLS, CALDAV_MAX_EVENTS, CALDAV_READ_ONLY, CALDAV_TIMEZONE, CALDAV_URL, CALDAV_USER_EMAIL, CALDAV_USERNAME, ELICITATION- Where it talks to
- ni-c.de (its own)Also example.net, elsewhere.example, calendarserver.org, apple.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names example.net, elsewhere.example, calendarserver.org, apple.com as well as its own vendor. The guard injects CALDAV_PASSWORD, CALDAV_TOKEN only into requests to ni-c.de (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 7 s · 2 scenarios · 0 deviationsStatic findings
* `https://x:[email protected]/` satisfied "same origin" and would have beenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `https://x:[email protected]/` satisfied "same origin" and would have beenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// userinfo, so `https://x:y@host/` on the right host passed here and itsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// credentials — "https://admin:s3cret@host:99999", an out-of-range port —Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `=TRUE` from a Windows environment, a trailing space from a copied `.env` line:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @ni-c/caldav-mcp@0.1.5 as of 2d ago. This is the package itself, not its dependencies.