Is iMessage MCP safe to use?

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

What is the trust score for iMessage MCP?

iMessage MCP scores 70.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 24 GitHub stars and is categorized under MCP Servers.

iMessage MCP

anipotts/imessage-mcp

Private, read-only MCP for Apple Messages on Mac.

MCP Servers TypeScript Grade B Listed MIT

70.8/100

Rank #210 of 1320

Compare iMessage MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-31 · 4d ago

Recent change

Rank +1

Is iMessage MCP safe? iMessage MCP scores 70.8/100 (Grade B), ranked #210 of 1320 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 2.9/10; 36% of recent commits are signed; last pushed 2026-08-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#102 Streamdeck MCP — 71.0 (B) → #103 Wireshark MCP — 71.0 (B) → #105 Apple Mail MCP — 70.7 (B) → #106 Keboola MCP Server — 70.6 (B) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-08-31

Rank Moved

Rank dropped 24 spots (#162 → #186)

2026-08-30

Rank Moved

Rank rose 12 spots (#174 → #162)

2026-08-27

Mcp Status Changed

Detected MCP server support changed: implemented → declared

Maintainer Checklist

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

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 iMessage MCP View MCP Servers Report missing data

58.8

Activity sub-score · out of 100

#104

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

Activity & Reach

Stars

Forks

Last Push

2026-08-31

4 days ago

Commits (4 wk)

Downloads (7d)

975

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼7

was #203

Analysis

HVTrust Dimensions vs MCP Servers

70.8 / 100 · 100.0% confidence

iMessage MCP MCP Servers average (778 agents)

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

12.9 / 25

3.3 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.0 / 17

0.8 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

18.9 / 20

6.7 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.3 / 20

1.0 above avg 6.3

Activity Inputs

58.8 / 100

StarsRepository reach

8.4 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

22.4 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Aug 26, 2026

Signed Commits

36%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 3

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is iMessage MCP safe?

iMessage MCP 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 iMessage MCP publish package provenance?

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

Does iMessage MCP have an OpenSSF Scorecard?

iMessage MCP has an OpenSSF Scorecard score of 2.9/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 iMessage MCP actively maintained?

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

What license does iMessage MCP use?

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

Are iMessage MCP's commits signed?

36% of the last 100 commits to iMessage 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 iMessage 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-08-27

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-08-27

Provenance Added

Package provenance attestation detected

Maintain iMessage MCP?

For maintainers

HVTrust scores iMessage 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-08-31

Rank Moved

Rank dropped 24 spots (#162 → #186)

2026-08-30

Rank Moved

Rank rose 12 spots (#174 → #162)

2026-08-27

Mcp Status Changed

Detected MCP server support changed: implemented → declared

2026-08-27

Provenance Added

Package provenance attestation detected

2026-08-27

Grade Changed

Trust grade D → B

2026-08-27

Rank Moved

Rank rose 380 spots (#547 → #167)

2026-08-27

HVTrust Changed

HVTrust up 21.2pts (49.1 → 70.3)

2026-08-27

Activity Score Changed

Activity score up 23pts (36 → 59)

2026-08-26

Scorecard Added

OSSF Scorecard: 2.9/10

2026-08-26

Rank Moved

Rank rose 238 spots (#785 → #547)

2026-08-26

HVTrust Changed

HVTrust up 19.3pts (29.8 → 49.1)

2026-08-16

Rank Moved

Rank dropped 17 spots (#768 → #785)

2026-08-10

HVTrust Changed

HVTrust up 4.0pts (26.5 → 30.5)

2026-08-10

Activity Score Changed

Activity score up 12pts (23 → 36)

2026-08-08

Newly Listed

First tracked at rank #762

GitHub → npm: imessage-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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