Apple Docs MCP
MCP server for Apple Developer Documentation - Search iOS/macOS/SwiftUI/UIKit docs, WWDC videos, Swift/Objective-C APIs & code examples in Claude, Cursor & AI assistants
Is Apple Docs MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Apple Docs MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Apple Docs MCP scores 42.8/100 (Grade D), ranked #1104 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.7/10; 12% of recent commits are signed; last pushed 2026-03-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How Apple Docs MCP compares in MCP Servers
- #647 Opendocswork MCP 43.0 +0.2
- #648 Ux MCP Server 42.9 +0.1
- #649 Apple Docs MCP 42.8 this agent
- #650 Flstudio MCP 42.8 ±0
- #651 Excel MCP Server 42.7 −0.1
Bars show each HVTrust score; the tick marks Apple Docs MCP’s 42.8.
Where the 42.8 comes from
HVTrust dimensions vs the MCP Servers average
42.8 / 100 · 100.0% confidenceApple Docs MCP MCP Servers average (775 agents)
Quick Trust Read
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 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
Activity & Reach
Analysis
Activity Inputs
27.4 / 100Supply Chain Trust
Common questions about Apple Docs MCP
Does Apple Docs MCP publish package provenance?
Does Apple Docs MCP have an OpenSSF Scorecard?
Is Apple Docs MCP actively maintained?
What license does Apple Docs MCP use?
Are Apple Docs MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Apple Docs 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.
Maintain Apple Docs MCP?
For maintainers
HVTrust scores Apple Docs 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/apple-docs-mcp)
<a href="https://hvtracker.net/agents/apple-docs-mcp"><img src="https://hvtracker.net/badge/apple-docs-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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