updated 2026-09-04 13:33 UTC

MacOS MCP

CursorTouch/MacOS-MCP

Lightweight MCP server for computer use in MacOS

MCP Servers Python Grade D Listed MIT
23.0/100
Rank #1273 of 1320
Compare MacOS MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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-08-27 · 8d ago
Recent change
Rank +6

Is MacOS MCP safe? MacOS MCP scores 23.0/100 (Grade D), ranked #1273 of 1320 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; 25% of recent commits are signed; last pushed 2026-08-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#746 Mondaycom MCP — 23.5 (D) → #747 MCP Drawthings — 23.2 (D) → #749 Awesome Copilot MCP Server — 22.8 (D) → #750 OpenSTAAD MCP Server — 22.4 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 32 spots (#1234 → #1266)
2026-09-02
Rank Moved
Rank dropped 37 spots (#1197 → #1234)
2026-09-01
Rank Moved
Rank dropped 50 spots (#1147 → #1197)
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.
Compare with another agent Get email alerts for MacOS MCP View MCP Servers Report missing data
62.2
Activity sub-score · out of 100
#748
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 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-09-04 13:33 UTC · Repo last pushed 8 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
166
Forks
25
Last Push
2026-08-27
8 days ago
Commits (4 wk)
29
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▼7
was #1266

Analysis

HVTrust Dimensions vs MCP Servers

23.0 / 100 · 50.0% confidence

MacOS MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.2 / 25
8.3 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
5.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.3 / 20
0.9 below avg 6.2

Activity Inputs

62.2 / 100
StarsRepository reach
13.3 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
18.4 / 25
CommunityFork signal
6.6 / 20

Supply Chain Trust

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

Is MacOS MCP safe?

Public trust evidence for MacOS MCP 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 MCP publish package provenance?
No published build provenance is currently detected for MacOS MCP. 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 MCP have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MacOS MCP. 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 MCP actively maintained?
Maintained. Last push was 8 days ago.
What license does MacOS MCP use?
MacOS MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MacOS MCP's commits signed?
25% of the last 100 commits to MacOS 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
MacOS 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
high confidence
Extensions
Extension based 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 MCP?

For maintainers

HVTrust scores MacOS 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
Rank 16Listed 1
2026-09-03
Rank Moved
Rank dropped 32 spots (#1234 → #1266)
2026-09-02
Rank Moved
Rank dropped 37 spots (#1197 → #1234)
2026-09-01
Rank Moved
Rank dropped 50 spots (#1147 → #1197)
2026-08-31
Rank Moved
Rank dropped 34 spots (#1113 → #1147)
2026-08-30
Rank Moved
Rank dropped 42 spots (#1071 → #1113)
2026-08-29
Rank Moved
Rank dropped 48 spots (#1023 → #1071)
2026-08-28
Rank Moved
Rank dropped 33 spots (#990 → #1023)
2026-08-27
Rank Moved
Rank dropped 23 spots (#967 → #990)
2026-08-26
Rank Moved
Rank dropped 104 spots (#863 → #967)
2026-08-25
Rank Moved
Rank rose 10 spots (#873 → #863)
2026-08-24
Rank Moved
Rank dropped 10 spots (#863 → #873)
2026-08-19
Rank Moved
Rank dropped 11 spots (#863 → #874)
2026-08-16
Rank Moved
Rank dropped 17 spots (#857 → #874)
2026-08-13
Rank Moved
Rank dropped 11 spots (#847 → #858)
2026-08-12
Rank Moved
Rank rose 18 spots (#865 → #847)
2026-08-10
Rank Moved
Rank dropped 49 spots (#817 → #866)
2026-08-08
Newly Listed
First tracked at rank #813
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 23.0 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/macos-mcp.svg)](https://hvtracker.net/agents/macos-mcp)
HTML:
<a href="https://hvtracker.net/agents/macos-mcp"><img src="https://hvtracker.net/badge/macos-mcp.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