macOS Calendar and Reminders
macOS Calendar & Reminders MCP server (29 tools) — native Swift EventKit for Claude Desktop & Code. Events + reminders CRUD, recurring, batch ops, conflict & duplicate detection, per-event timezone, undo/redo, #tags, --cli mode, SwiftUI --setup TCC flow, --self-update. Developer-ID signed +…
Is macOS Calendar and Reminders safe? Promising trust profile, but some evidence still deserves review.
Compare macOS Calendar and Reminders
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: macOS Calendar and Reminders scores 56.3/100 (Grade C), ranked #739 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.2/10; 26% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How macOS Calendar and Reminders compares in MCP Servers
- #407 Cross Code Organizer 56.3 ±0
- #408 MCP Arr 56.3 ±0
- #409 macOS Calendar and Reminders 56.3 this agent
- #410 Kernel MCP Server 56.3 ±0
- #411 State Memory MCP 56.3 ±0
Bars show each HVTrust score; the tick marks macOS Calendar and Reminders’s 56.3.
Where the 56.3 comes from
HVTrust dimensions vs the MCP Servers average
56.3 / 100 · 100.0% confidencemacOS Calendar and Reminders MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
61.7 / 100Supply Chain Trust
Common questions about macOS Calendar and Reminders
Does macOS Calendar and Reminders publish package provenance?
Does macOS Calendar and Reminders have an OpenSSF Scorecard?
Is macOS Calendar and Reminders actively maintained?
What license does macOS Calendar and Reminders use?
Are macOS Calendar and Reminders's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to macOS Calendar and Reminders'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.
Maintain macOS Calendar and Reminders?
For maintainers
HVTrust scores macOS Calendar and Reminders 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/macos-calendar-and-reminders)
<a href="https://hvtracker.net/agents/macos-calendar-and-reminders"><img src="https://hvtracker.net/badge/macos-calendar-and-reminders.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON