Is iMessage MCP safe to use?

iMessage MCP has an HVTrust score of 78.1/100 (Grade B), ranked #220 of 1374 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 78.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 31 GitHub stars and is categorized under MCP Servers.

iMessage MCP

Repository

Search and read your Messages history from Claude, Codex, Cursor, VS Code, and any other MCP client.

MCP Servers TypeScript Listed MIT

Is iMessage MCP safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.1 / 10

Provenance Attested

Signed commits 100%

Last push yesterday

Advisories None known

Compare iMessage MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: iMessage MCP scores 78.1/100 (Grade B), ranked #220 of 1374 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 7.1/10; 100% of recent commits are signed; no published advisory affects its latest release (imessage-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How iMessage MCP 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 7.1 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +4.0 → 82.1 A · #63 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Signed

github.com/anipotts/imessage-mcp, MIT, last pushed 2026-11-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Strong

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

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 9

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 10
Published packages Partly attested
- npm imessage-mcp Source link points to this repo's current name Build provenance attested
What you install today No known advisories

Latest release checked: imessage-mcp 3.3.2. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-27 Package provenance attestation detected
2026-08-26 OSSF Scorecard: 2.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues iMessage MCP’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 iMessage MCP compares in MCP Servers

#124 Email MCP 78.2 +0.1
#125 Universal Screenshot MCP 78.2 +0.1
#126 iMessage MCP 78.1 this agent
#127 Delimit — API Governance for AI Coding Assistants 78.1 ±0
#128 Yazio MCP 78.0 −0.1

Bars show each HVTrust score; the tick marks iMessage MCP’s 78.1.

Where the 78.1 comes from

HVTrust dimensions vs the MCP Servers average

78.1 / 100 · 100.0% confidence

iMessage MCP MCP Servers average (778 agents)

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

21.4 / 25

10.6 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.2 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

18.1 / 20

5.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

7.4 / 20

in line with avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-09

Rank Moved

Rank rose 11 spots (#229 → #218)

2026-11-03

Rank Moved

Rank dropped 16 spots (#197 → #213)

2026-10-29

Rank Moved

Rank rose 11 spots (#210 → #199)

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent View MCP Servers Report missing data

57.7

Activity sub-score · out of 100

#126

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-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-09

yesterday

Commits (4 wk)

Downloads (7d)

638

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #218

Analysis

Activity Inputs

57.7 / 100

StarsRepository reach

9.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

19.3 / 25

CommunityFork signal

4.4 / 20

Common questions about iMessage MCP

Public supply-chain signals for iMessage MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but iMessage MCP carries less obvious unverified-evidence risk than projects with thin signals.

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 7.1/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 1 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?

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

low confidence

Unknown

Package source metadata is missing or inconclusive

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

2026-09-23

Provenance Added

Package provenance attestation detected

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

Rank Moved

Rank rose 11 spots (#229 → #218)

2026-11-03

Rank Moved

Rank dropped 16 spots (#197 → #213)

2026-10-29

Rank Moved

Rank rose 11 spots (#210 → #199)

2026-10-27

Rank Moved

Rank dropped 12 spots (#198 → #210)

2026-10-26

Rank Moved

Rank rose 12 spots (#210 → #198)

2026-10-24

Grade Changed

Trust grade A → B

2026-10-24

Rank Moved

Rank dropped 77 spots (#130 → #207)

2026-10-24

HVTrust Changed

HVTrust down 4.4pts (81.9 → 77.5)

2026-10-14

Rank Moved

Rank dropped 12 spots (#113 → #125)

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

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 532 spots (#634 → #102)

2026-09-23

HVTrust Changed

HVTrust up 50.7pts (32.7 → 83.4)

2026-09-22

Newly Listed

First tracked at rank #634

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Grade Changed

Trust grade B → A

2026-09-19

Rank Moved

Rank rose 129 spots (#225 → #96)

2026-09-19

HVTrust Changed

HVTrust up 8.5pts (75.2 → 83.7)

2026-09-18

Rank Moved

Rank rose 12 spots (#237 → #225)

2026-09-17

Rank Moved

Rank dropped 20 spots (#217 → #237)

2026-09-14

Rank Moved

Rank rose 65 spots (#281 → #216)

2026-09-14

HVTrust Changed

HVTrust up 3.1pts (72.3 → 75.4)

2026-09-09

Rank Moved

Rank rose 35 spots (#305 → #270)

2026-09-08

Rank Moved

Rank dropped 22 spots (#283 → #305)

2026-09-07

Rank Moved

Rank dropped 10 spots (#273 → #283)

2026-09-05

Rank Moved

Rank dropped 59 spots (#210 → #269)

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)

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.4 · Raw JSON

iMessage MCP

How iMessage MCP could raise its score

Chain of custody

Source Signed

Review and release Strong

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How iMessage MCP compares in MCP Servers

Where the 78.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about iMessage MCP

AI agent surface

Maintain iMessage MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers