Is Caldav MCP safe to use?

Caldav MCP has an HVTrust score of 77.1/100 (Grade B), ranked #186 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Caldav MCP?

Caldav MCP scores 77.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 101 GitHub stars and is categorized under MCP Servers.

Caldav MCP

dominik1001/caldav-mcp

🗓️ A CalDAV Model Context Protocol (MCP) server to expose calendar operations as tools for AI assistants.

MCP Servers TypeScript Listed MIT

Is Caldav MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 79%

Last push 5d ago

Compare Caldav MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Caldav MCP scores 77.1/100 (Grade B), ranked #186 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 79% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Caldav MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Caldav MCP’s 77.1.

Where the 77.1 comes from

HVTrust dimensions vs the MCP Servers average

77.1 / 100 · 100.0% confidence

Caldav MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.3 / 25

8.0 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

1.0 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.3 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.2 / 20

1.0 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for Caldav MCP View MCP Servers Report missing data

54.1

Activity sub-score · out of 100

#105

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

101

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

347

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #186

Analysis

Activity Inputs

54.1 / 100

StarsRepository reach

12.1 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

7.2 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

79%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Caldav MCP

Public supply-chain signals for Caldav MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Caldav MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Caldav MCP publish package provenance?

Yes. Caldav MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Caldav MCP have an OpenSSF Scorecard?

Caldav MCP has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Caldav MCP actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Caldav MCP use?

Caldav MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Caldav MCP's commits signed?

79% of the last 100 commits to Caldav MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Caldav MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Caldav MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Caldav MCP?

For maintainers

HVTrust scores Caldav MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 647 spots (#827 → #180)

2026-09-23

HVTrust Changed

HVTrust up 49.0pts (28.3 → 77.3)

2026-09-22

Newly Listed

First tracked at rank #827

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 10 spots (#185 → #175)

2026-09-11

Scorecard Added

OSSF Scorecard: 5.5/10

2026-09-11

Rank Moved

Rank rose 243 spots (#418 → #175)

2026-09-11

HVTrust Changed

HVTrust up 11.5pts (65.8 → 77.3)

2026-09-07

Grade Changed

Trust grade D → B

2026-09-07

Rank Moved

Rank rose 634 spots (#1037 → #403)

2026-09-07

HVTrust Changed

HVTrust up 22.7pts (43.2 → 65.9)

2026-09-06

Rank Moved

Rank dropped 12 spots (#1025 → #1037)

2026-09-05

Rank Moved

Rank dropped 45 spots (#980 → #1025)

2026-09-04

Rank Moved

Rank dropped 27 spots (#953 → #980)

2026-09-03

Rank Moved

Rank dropped 57 spots (#896 → #953)

2026-09-02

Rank Moved

Rank dropped 47 spots (#849 → #896)

2026-09-01

Rank Moved

Rank dropped 31 spots (#818 → #849)

2026-08-31

Rank Moved

Rank dropped 27 spots (#791 → #818)

2026-08-30

Rank Moved

Rank dropped 30 spots (#761 → #791)

2026-08-29

Rank Moved

Rank dropped 48 spots (#713 → #761)

2026-08-28

Rank Moved

Rank dropped 25 spots (#688 → #713)

2026-08-27

Rank Moved

Rank dropped 22 spots (#666 → #688)

2026-08-26

Rank Moved

Rank dropped 99 spots (#567 → #666)

2026-08-22

Rank Moved

Rank rose 10 spots (#573 → #563)

2026-08-19

Rank Moved

Rank dropped 10 spots (#568 → #578)

2026-08-10

Rank Moved

Rank dropped 16 spots (#540 → #556)

2026-08-08

Newly Listed

First tracked at rank #540

GitHub → npm: caldav-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/caldav-mcp.svg)](https://hvtracker.net/agents/caldav-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/caldav-mcp"><img src="https://hvtracker.net/badge/caldav-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON