Is macOS Calendar and Reminders safe to use?

macOS Calendar and Reminders has an HVTrust score of 60.7/100 (Grade C), ranked #683 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for macOS Calendar and Reminders?

macOS Calendar and Reminders scores 60.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 45 GitHub stars and is categorized under MCP Servers.

macOS Calendar and Reminders

Repository

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 +…

MCP Servers Swift Listed MIT

Is macOS Calendar and Reminders safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.4 / 10

Provenance None

Signed commits 89%

Last push 2d ago

Compare macOS Calendar and Reminders

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: macOS Calendar and Reminders scores 60.7/100 (Grade C), ranked #683 of 1387 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.4/10; 89% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How macOS Calendar and Reminders could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.4 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +7.5 → 68.2 B · #247 of 779
Sign every commit89% signed today +0.6 → 61.3 C · #364 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships macOS Calendar and Reminders and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/PsychQuant/che-ical-mcp, MIT, last pushed 2026-11-09. 89% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.4/10 (scanned Nov 2, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10
Published packages None

No registry package. macOS Calendar and Reminders is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-09-03 OSSF Scorecard: 5.4/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues macOS Calendar and Reminders’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How macOS Calendar and Reminders compares in MCP Servers

#371 Power BI Modeling MCP Server 60.8 +0.1
#372 MCP File Tools 60.7 ±0
#373 macOS Calendar and Reminders 60.7 this agent
#374 Webhook MCP Server 60.7 ±0
#375 Yahoo Finance 60.6 −0.1

Bars show each HVTrust score; the tick marks macOS Calendar and Reminders’s 60.7.

Where the 60.7 comes from

HVTrust dimensions vs the MCP Servers average

60.7 / 100 · 100.0% confidence

macOS Calendar and Reminders MCP Servers average (779 agents)

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

11.2 / 25

in line with avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.1 / 17

0.8 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.6 above avg 12.3

AdoptionLog-scaled stars · package downloads

4.0 / 20

3.6 below avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-09

Rank Moved

Rank rose 38 spots (#715 → #677)

2026-11-07

Rank Moved

Rank rose 20 spots (#736 → #716)

2026-11-05

Rank Moved

Rank rose 54 spots (#791 → #737)

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent View MCP Servers Report missing data

64.6

Activity sub-score · out of 100

#373

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 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

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-09

2 days ago

Commits (4 wk)

185

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #685

Analysis

Activity Inputs

64.6 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

4.7 / 20

Common questions about macOS Calendar and Reminders

macOS Calendar and Reminders has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does macOS Calendar and Reminders publish package provenance?

No published build provenance is currently detected for macOS Calendar and Reminders. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does macOS Calendar and Reminders have an OpenSSF Scorecard?

macOS Calendar and Reminders has an OpenSSF Scorecard score of 5.4/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 macOS Calendar and Reminders actively maintained?

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

What license does macOS Calendar and Reminders use?

macOS Calendar and Reminders ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are macOS Calendar and Reminders's commits signed?

89% of the last 100 commits to macOS Calendar and Reminders 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

medium confidence

Implemented

macOS Calendar and Reminders appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 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.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-09

Rank Moved

Rank rose 38 spots (#715 → #677)

2026-11-07

Rank Moved

Rank rose 20 spots (#736 → #716)

2026-11-05

Rank Moved

Rank rose 54 spots (#791 → #737)

2026-10-19

Rank Moved

Rank rose 11 spots (#784 → #773)

2026-10-06

Rank Moved

Rank dropped 23 spots (#748 → #771)

2026-10-04

Rank Moved

Rank rose 25 spots (#769 → #744)

2026-10-02

Rank Moved

Rank dropped 12 spots (#759 → #771)

2026-09-30

Rank Moved

Rank dropped 15 spots (#746 → #761)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 271 spots (#459 → #730)

2026-09-23

HVTrust Changed

HVTrust up 12.5pts (43.9 → 56.4)

2026-09-22

Newly Listed

First tracked at rank #459

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 10 spots (#748 → #758)

2026-09-15

Rank Moved

Rank dropped 11 spots (#738 → #749)

2026-09-09

Rank Moved

Rank dropped 25 spots (#690 → #715)

2026-09-08

Rank Moved

Rank rose 35 spots (#725 → #690)

2026-09-08

Activity Score Changed

Activity score up 6pts (56 → 62)

2026-09-07

Rank Moved

Rank dropped 16 spots (#709 → #725)

2026-09-05

Rank Moved

Rank dropped 67 spots (#636 → #703)

2026-09-04

Rank Moved

Rank dropped 21 spots (#615 → #636)

2026-09-03

Scorecard Added

OSSF Scorecard: 5.4/10

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 632 spots (#1247 → #615)

2026-09-03

HVTrust Changed

HVTrust up 32.1pts (22.4 → 54.5)

2026-09-02

Rank Moved

Rank dropped 33 spots (#1214 → #1247)

2026-09-01

Rank Moved

Rank dropped 30 spots (#1184 → #1214)

2026-08-31

Rank Moved

Rank rose 62 spots (#1246 → #1184)

2026-08-31

HVTrust Changed

HVTrust up 3.9pts (18.6 → 22.5)

2026-08-31

Activity Score Changed

Activity score up 21pts (32 → 53)

2026-08-30

Rank Moved

Rank dropped 13 spots (#1233 → #1246)

2026-08-29

Rank Moved

Rank dropped 17 spots (#1216 → #1233)

2026-08-28

Rank Moved

Rank dropped 16 spots (#1200 → #1216)

2026-08-27

Rank Moved

Rank dropped 13 spots (#1187 → #1200)

2026-08-26

Rank Moved

Rank dropped 44 spots (#1143 → #1187)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1107 → #1133)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/macos-calendar-and-reminders.svg)](https://hvtracker.net/agents/macos-calendar-and-reminders)
            
HTML:
            <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

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

macOS Calendar and Reminders

How macOS Calendar and Reminders could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How macOS Calendar and Reminders compares in MCP Servers

Where the 60.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about macOS Calendar and Reminders

AI agent surface

Maintain macOS Calendar and Reminders?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers