XcodeBuildMCP

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 5.1 / 10
Provenance Attested
Signed commits 64%
Last push 4d ago
Advisories None known
Compare XcodeBuildMCP
Suggest a correction

In detail: XcodeBuildMCP scores 79.1/100 (Grade B), ranked #178 of 1371 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 5.1/10; 64% of recent commits are signed; no published advisory affects its latest release (xcodebuildmcp); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Chain of custody

Scanners check what the code says. This traces who ships XcodeBuildMCP 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.

  1. Source Partly signed

    github.com/getsentry/MobileBuildMCP, MIT, last pushed 2026-10-09. 64% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Oct 12, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection1
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 3
    SAST 9
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Partly attested

    • npm xcodebuildmcp Source link points to getsentry/xcodebuildmcp, same owner Build provenance attested
  4. What you install today No known advisories

    Latest release checked: xcodebuildmcp 2.7.0. No published advisory affects it (OSV, checked 2026-10-13).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of XcodeBuildMCP.

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

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 XcodeBuildMCP compares in MCP Servers

  1. #91 Substack MCP Server 79.1 ±0
  2. #92 Sec Edgar MCP 79.1 ±0
  3. #93 XcodeBuildMCP 79.1 this agent
  4. #94 CrowdStrike Falcon MCP Server 79.0 −0.1
  5. #95 Better Godot MCP 79.0 −0.1

Bars show each HVTrust score; the tick marks XcodeBuildMCP’s 79.1.

Where the 79.1 comes from

HVTrust dimensions vs the MCP Servers average

79.1 / 100 · 100.0% confidence

XcodeBuildMCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.1 / 25
6.7 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.6 / 20
1.4 above avg 12.2
AdoptionLog-scaled stars · package downloads
15.6 / 20
8.2 above avg 7.4

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-10-03
Grade Changed
Trust grade A → B
2026-10-03
Rank Moved
Rank dropped 56 spots (#107 → #163)
2026-10-03
HVTrust Changed
HVTrust down 4.1pts (83.3 → 79.2)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
70.9
Activity sub-score · out of 100
#93

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 →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed 4 days ago

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
6.5k
Forks
323
Last Push
2026-10-09
4 days ago
Commits (4 wk)
8?
Downloads (7d)
66,474
npm
HN mentions (30d)
—
Open Issues
16
Rank Change
▼1
was #177

Analysis

Activity Inputs

70.9 / 100
StarsRepository reach
22.9 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
11.7 / 20

Common questions about XcodeBuildMCP

Public supply-chain signals for XcodeBuildMCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but XcodeBuildMCP carries less obvious unverified-evidence risk than projects with thin signals.
Does XcodeBuildMCP publish package provenance?
Yes. XcodeBuildMCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does XcodeBuildMCP have an OpenSSF Scorecard?
XcodeBuildMCP has an OpenSSF Scorecard score of 5.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 XcodeBuildMCP actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does XcodeBuildMCP use?
XcodeBuildMCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are XcodeBuildMCP's commits signed?
64% of the last 100 commits to XcodeBuildMCP 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
XcodeBuildMCP 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
None detected
No clear plugin system or broad tool 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

Maintain XcodeBuildMCP?

For maintainers

HVTrust scores XcodeBuildMCP 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
Rank 8Score 3HVTrust 3Grade 3
2026-10-03
Grade Changed
Trust grade A → B
2026-10-03
Rank Moved
Rank dropped 56 spots (#107 → #163)
2026-10-03
HVTrust Changed
HVTrust down 4.1pts (83.3 → 79.2)
2026-09-23
Rank Moved
Rank dropped 44 spots (#70 → #114)
2026-09-23
Activity Score Changed
Activity score up 10pts (58 → 68)
2026-09-21
Rank Moved
Rank rose 66 spots (#136 → #70)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 631 spots (#733 → #102)
2026-09-05
HVTrust Changed
HVTrust up 29.9pts (51.8 → 81.7)
2026-09-04
Rank Moved
Rank dropped 28 spots (#705 → #733)
2026-09-03
Rank Moved
Rank dropped 37 spots (#668 → #705)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 573 spots (#95 → #668)
2026-09-02
HVTrust Changed
HVTrust down 28.6pts (80.5 → 51.9)
2026-09-01
Rank Moved
Rank dropped 18 spots (#77 → #95)
2026-09-01
Activity Score Changed
Activity score down 8pts (67 → 59)
2026-08-22
Activity Score Changed
Activity score down 6pts (71 → 66)

Embed Badge Badge guide for maintainers →

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