{"id":"philflowio-dav-mcp","name":"dav-mcp","af_score":69.8,"security_score":60.5,"reliability_score":36.2,"what_it_does":"dav-mcp provides an MCP server (and optionally an HTTP interface) that exposes CalDAV (calendar), CardDAV (contacts), and VTODO/VTODO-over-CalDAV-style (tasks) operations as a set of agent-callable tools for creating, updating, querying, and deleting calendar, contact, and todo resources on a DAV server.","best_when":"You want LLM/MCP-driven orchestration over calendar/contacts/tasks on an RFC-compliant CalDAV/CardDAV/VTODO server and can supply credentials via environment variables or configured MCP runtime.","avoid_when":"You cannot control or secure outbound credentials/requests, or you need strongly specified retry/idempotency and pagination/error-code contracts (not fully evidenced in README).","last_evaluated":"2026-03-30T15:37:32.994870+00:00","has_mcp":true,"has_api":true,"auth_methods":["Bearer token for HTTP mode","OAuth2 for Google Calendar (via env configuration)"],"has_free_tier":false,"known_gotchas":["Write operations (create/update/delete) are exposed; without documented idempotency, agents may cause duplicate records if retries occur.","HTTP endpoint is localhost in examples; remote deployments should ensure correct routing and secure exposure.","DAV servers can differ in RFC feature completeness; some queries/filters may behave differently by provider even if the tool exists.","Agents may need to use the *_query tools for filtering rather than listing-all tools to avoid excessive data retrieval."],"error_quality":0.0}