macOS Calendar and Reminders

macOS Calendar & Reminders MCP server (29 tools) — native Swift EventKit for Claude Desktop & Code. Events + reminders C

MCP Servers Swift Grade D Listed MIT
19.1/100
Rank #1110 of 1283
Compare macOS Calendar and Reminders

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-10 · 33d ago
Recent change
Rank +2

Is macOS Calendar and Reminders safe? macOS Calendar and Reminders scores 19.1/100 (Grade D), ranked #1110 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 41% of recent commits are signed; last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 68 spots (#1040 → #1108)
2026-08-09
Activity Score Changed
Activity score down 11pts (45 → 34)
2026-08-08
Newly Listed
First tracked at rank #958
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 33 days ago. Fresh activity helps separate stable projects from stale ones.
34.2
Activity sub-score · out of 100
#622

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

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 33 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
33
Forks
8
Last Push
2026-07-10
33 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
2
Rank Change
▼1
was #1109

Analysis

HVTrust Dimensions vs MCP Servers

19.1 / 100 · 50.0% confidence

macOS Calendar and Reminders MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.1 / 25
2.9 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
9.8 / 20
2.6 below avg 12.4
AdoptionLog-scaled stars · package downloads
3.7 / 20
2.1 below avg 5.8

Activity Inputs

34.2 / 100
StarsRepository reach
9.2 / 30
FreshnessLast push recency
20.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
Not available
Signed Commits
41%
of last 100 commits verified

Is macOS Calendar and Reminders safe?

Public trust evidence for macOS Calendar and Reminders is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
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?
No OpenSSF Scorecard data is currently published for macOS Calendar and Reminders. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is macOS Calendar and Reminders actively maintained?
Slowing down. Last push was 33 days ago — keep an eye on whether activity resumes.
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?
41% 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.
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

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
Listed 1Score 1Rank 1
2026-08-10
Rank Moved
Rank dropped 68 spots (#1040 → #1108)
2026-08-09
Activity Score Changed
Activity score down 11pts (45 → 34)
2026-08-08
Newly Listed
First tracked at rank #958

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 19.1 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON