doublespeed — Xcode as an API
NPM · @DOUBLESPEED/MCP · SCANNED SEP 20
Build, test and run iOS apps on a remote Mac from any machine. XcodeBuildMCP-compatible tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1583 tokens (~143/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the doublespeed — Xcode as an API MCP server?
doublespeed — Xcode as an API runs locally as an npm package, launched with npx -y @doublespeed/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @doublespeed/mcp
claude mcp add ai-doublespeed-mcp -- npx -y @doublespeed/mcp
{
"mcpServers": {
"ai-doublespeed-mcp": {
"command": "npx",
"args": [
"-y",
"@doublespeed/mcp"
]
}
}
} {
"servers": {
"ai-doublespeed-mcp": {
"command": "npx",
"args": [
"-y",
"@doublespeed/mcp"
]
}
}
} codex mcp add ai-doublespeed-mcp -- npx -y @doublespeed/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-doublespeed-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@doublespeed/mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-doublespeed-mcp --command npx --arg -y --arg @doublespeed/mcp
mcp_servers:
ai-doublespeed-mcp:
command: "npx"
args: ["-y", "@doublespeed/mcp"] {
"McpServers": {
"ai-doublespeed-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@doublespeed/mcp"
]
}
}
} assistant mcp add ai-doublespeed-mcp -t stdio -c npx -a -y @doublespeed/mcp
{
"mcpServers": {
"ai-doublespeed-mcp": {
"command": "npx",
"args": [
"-y",
"@doublespeed/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@doublespeed/mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
archive_app Archive (.xcarchive) ~247
Produce an unsigned .xcarchive for the device SDK on the fleet (Release). Signing and TestFlight upload are not available yet.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Debug or Release (default: what the scheme defines) |
| extraArgs | array | – | Extra `ds xcode` flags, e.g. ['--setting', 'CODE_SIGNING_ALLOWED=NO', '--timeout', '3600'] |
| projectPath | string | – | Path to the .xcodeproj (omit for a workspace or a Swift package) |
| scheme | string | – | Scheme to build; inferred when the project has exactly one app scheme |
| simulatorName | string | – | Simulator device name, e.g. 'iPhone 16 Pro' (default iPhone 16) |
| workspacePath | string | – | Path to the .xcworkspace (CocoaPods / React Native projects) |
| workspaceRoot | string | – | Directory to upload as the project root (default: the directory containing the project/workspace, or the current directory). Only files under it are sent. |
| xcodeVersion | string | – | Required Xcode major or exact version, e.g. '16' or '16.4' |
No output schema declared.
No examples provided.
build_run_sim Build and run in a live simulator ~305
Build, install and launch the app in an iOS Simulator on the fleet and return a browser URL where a human can see and use it (tap, type, swipe). The session stays open until stop_app_sim or the idle timeout. Billed per second while open.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Debug or Release (default: what the scheme defines) |
| extraArgs | array | – | Extra `ds xcode` flags, e.g. ['--setting', 'CODE_SIGNING_ALLOWED=NO', '--timeout', '3600'] |
| idleTimeoutSeconds | number | – | End the session after this long with no viewer activity (60–7200, default 900) |
| projectPath | string | – | Path to the .xcodeproj (omit for a workspace or a Swift package) |
| scheme | string | – | Scheme to build; inferred when the project has exactly one app scheme |
| simulatorName | string | – | Simulator device name, e.g. 'iPhone 16 Pro' (default iPhone 16) |
| workspacePath | string | – | Path to the .xcworkspace (CocoaPods / React Native projects) |
| workspaceRoot | string | – | Directory to upload as the project root (default: the directory containing the project/workspace, or the current directory). Only files under it are sent. |
| xcodeVersion | string | – | Required Xcode major or exact version, e.g. '16' or '16.4' |
No output schema declared.
No examples provided.
build_sim Build for iOS Simulator ~272
Compile the project for the iOS Simulator on a Mac in the doublespeed fleet. Returns file:line:col errors. Use when there is no Xcode locally.
| Name | Type | Req | Description |
|---|---|---|---|
| collectApp | boolean | – | Also upload the built .app as an artifact |
| configuration | string | – | Debug or Release (default: what the scheme defines) |
| extraArgs | array | – | Extra `ds xcode` flags, e.g. ['--setting', 'CODE_SIGNING_ALLOWED=NO', '--timeout', '3600'] |
| projectPath | string | – | Path to the .xcodeproj (omit for a workspace or a Swift package) |
| scheme | string | – | Scheme to build; inferred when the project has exactly one app scheme |
| simulatorName | string | – | Simulator device name, e.g. 'iPhone 16 Pro' (default iPhone 16) |
| workspacePath | string | – | Path to the .xcworkspace (CocoaPods / React Native projects) |
| workspaceRoot | string | – | Directory to upload as the project root (default: the directory containing the project/workspace, or the current directory). Only files under it are sent. |
| xcodeVersion | string | – | Required Xcode major or exact version, e.g. '16' or '16.4' |
No output schema declared.
No examples provided.
check_project Check project on a Mac (no API key needed) ~185
Lint-only check on a real Mac: resolves the project/workspace/package and schemes with xcodebuild -list, parses every Swift file with swiftc (syntax, file:line:col), lints plists. Does NOT compile. Works without DS_API_KEY (keyless trial: 10 per day per address, 25 MB snapshot). Use this to validate structure before asking the user for a key; use build_sim/test_sim for a real build.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Path to the .xcodeproj (omit for a workspace or a Swift package) |
| workspacePath | string | – | Path to the .xcworkspace (CocoaPods / React Native projects) |
| workspaceRoot | string | – | Directory to upload as the project root (default: the directory containing the project/workspace, or the current directory). Only files under it are sent. |
No output schema declared.
No examples provided.
discover_projs Discover Xcode projects ~67
Scan a directory for .xcworkspace, .xcodeproj and Package.swift (skipping node_modules, Pods, .build, DerivedData). Local; no Mac needed.
| Name | Type | Req | Description |
|---|---|---|---|
| maxDepth | number | – | – |
| workspaceRoot | string | – | Directory to scan (default: cwd) |
No output schema declared.
No examples provided.
doctor Doctor ~31
Check that this machine can reach the doublespeed fleet: key present, API reachable, fleet capabilities, ds CLI version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
job_status Job status / logs ~53
Fetch a previous job (status, error, diagnostics, tests) and optionally its log tail.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| logLines | number | – | Return the last N log lines (default 0) |
No output schema declared.
No examples provided.
list_schemes List schemes ~67
List shared schemes of a project or workspace by reading xcshareddata (local). Unshared schemes are not visible; if none are listed, ds infers the scheme from the app target on the Mac.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | – |
| workspacePath | string | – | – |
No output schema declared.
No examples provided.
list_sims List simulators ~28
List simulator devices, iOS runtimes and Xcode versions available on the doublespeed fleet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stop_app_sim Stop a simulator session ~43
End a live simulator session started by build_run_sim (frees the Mac; stops billing).
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by build_run_sim |
No output schema declared.
No examples provided.
test_sim Run tests on iOS Simulator ~285
Build and run XCTest / Swift Testing on an iOS Simulator on the doublespeed fleet. Returns per-test results and compile errors.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration | string | – | Debug or Release (default: what the scheme defines) |
| extraArgs | array | – | Extra `ds xcode` flags, e.g. ['--setting', 'CODE_SIGNING_ALLOWED=NO', '--timeout', '3600'] |
| onlyTesting | array | – | XCTest identifiers to run, e.g. ['AppTests/CounterTests'] |
| projectPath | string | – | Path to the .xcodeproj (omit for a workspace or a Swift package) |
| scheme | string | – | Scheme to build; inferred when the project has exactly one app scheme |
| simulatorName | string | – | Simulator device name, e.g. 'iPhone 16 Pro' (default iPhone 16) |
| skipTesting | array | – | – |
| testPlan | string | – | – |
| workspacePath | string | – | Path to the .xcworkspace (CocoaPods / React Native projects) |
| workspaceRoot | string | – | Directory to upload as the project root (default: the directory containing the project/workspace, or the current directory). Only files under it are sent. |
| xcodeVersion | string | – | Required Xcode major or exact version, e.g. '16' or '16.4' |
No output schema declared.
No examples provided.
What is the doublespeed — Xcode as an API MCP server?
doublespeed — Xcode as an API is an MCP server listed in the public MCP registry as ai.doublespeed/mcp. Build, test and run iOS apps on a remote Mac from any machine. XcodeBuildMCP-compatible tools. This page covers its npm package (@doublespeed/mcp).
Is the doublespeed — Xcode as an API MCP server safe to use?
doublespeed — Xcode as an API scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the doublespeed — Xcode as an API MCP server expose?
doublespeed — Xcode as an API exposes 11 tools: discover_projs, list_schemes, list_sims, check_project, build_sim, and 6 more. Their descriptions and schemas cost roughly 1,583 tokens of context every time the server is loaded.
Is the doublespeed — Xcode as an API MCP server still maintained?
doublespeed — Xcode as an API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the doublespeed — Xcode as an API MCP server under?
doublespeed — Xcode as an API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.