doublespeed MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Doublespeed remote Mac build and simulator tools: Does XcodeBuildMCP-compatible naming preserve remote fleet behavior without implying local filesystem access?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Build, test, archive and run iOS apps on remote managed Macs from non-Mac development environments.

What we know

XcodeBuildMCP-compatible MCP that uploads project workspace content to doublespeed's Mac fleet for project checks, simulator builds/tests, app launches and unsigned archives.

Maintenance / activity evidence

@doublespeed/mcp 0.1.1 published 2026-08-28T01:06:49.288Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Remote Mac build/test/run/archive authority over uploaded project. Writes: Submit build/test/archive jobs; Launch/stop live simulator sessions.
DS_API_KEY.
Sensitive access: Source code, Build artifacts, Potential embedded project secrets

Remote build service receives source; API key and workspace boundaries must be controlled.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does XcodeBuildMCP-compatible naming preserve remote fleet behavior without implying local filesystem access?

The bounded review of the publisher's documented Doublespeed remote Mac build and simulator tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Remote build service receives source; API key and workspace boundaries must be controlled.
Remote Mac build/test/run/archive authority over uploaded project.
DS_API_KEY.
Workspace files are uploaded content-addressed to the doublespeed Mac fleet; changed files are re-uploaded on later jobs.
Reviewed write actions: Submit build/test/archive jobs; Launch/stop live simulator sessions
Sensitive access: Source code, Build artifacts, Potential embedded project secrets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Most operations require DS_API_KEY and consume Mac time.
Only files under workspaceRoot are uploaded, but source code still leaves local machine.
Code signing/TestFlight and screenshot/accessibility capture are not yet supported.
Live simulator URL is intended for human inspection.

Original activity observations

@doublespeed/mcp 0.1.1 published 2026-08-28T01:06:49.288Z

Technical identity

npm/@doublespeed/mcp

Exact implementation source: https://www.npmjs.com/package/@doublespeed/mcp ↗
Reviewed resource type: MCP Server
Repository identity: doublespeed-main/mcp
Package identity: npm:@doublespeed/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@doublespeed/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
mac.doublespeed.ai/docs.md
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Node 20+. Publisher documents Claude mcp add with DS_API_KEY; check_project works keyless, other cloud-Mac tools require key.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add doublespeed -e DS_API_KEY=YOUR_KEY -- npx -y @doublespeed/mcp
Configure / authenticate
MCP100 setup guide
Publisher: `claude mcp add doublespeed -e DS_API_KEY=<key> -- npx -y @doublespeed/mcp`; Mac-only `check_project` works without a key.
Check connection
Suggested check
Use `check_project` for free local preflight; avoid remote paid Mac builds.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `doublespeed-mcp`, run `claude mcp remove doublespeed-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove doublespeed-mcp

Official Documentation & Sources

What it does

XcodeBuildMCP-compatible MCP that uploads project workspace content to doublespeed's Mac fleet for project checks, simulator builds/tests, app launches and unsigned archives.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Build, test, archive and run iOS apps on remote managed Macs from non-Mac development environments.

Representative uses

Discover Xcode projects/schemes
List fleet simulators/Xcode versions
Lint/check project without key
Build/test iOS simulator apps
Launch live simulator session
Create unsigned archive

Limitations

Most operations require DS_API_KEY and consume Mac time.
Only files under workspaceRoot are uploaded, but source code still leaves local machine.
Code signing/TestFlight and screenshot/accessibility capture are not yet supported.
Live simulator URL is intended for human inspection.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: DS_API_KEY.
Permissions: Remote Mac build/test/run/archive authority over uploaded project.
Data handling: Workspace files are uploaded content-addressed to the doublespeed Mac fleet; changed files are re-uploaded on later jobs.
Cost: usage_based
Risk and cautions: Remote build service receives source; API key and workspace boundaries must be controlled.

Access scope and cautions

Write actions: Submit build/test/archive jobs Launch/stop live simulator sessions
Sensitive access: Source code Build artifacts Potential embedded project secrets
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Discover Xcode projects/schemes; List fleet simulators/Xcode versions; Lint/check project without key; Build/test iOS simulator apps; Launch live simulator session; Create unsigned archive.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @doublespeed/mcp. Recorded transport: stdio. Recorded environment-variable notes: DS_API_KEY (required except check_project). No configuration values are supplied here. Prerequisites: Node 20+; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Doublespeed API key; `check_project` works keylessly. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

Documented write actions include: Submit build/test/archive jobs; Launch/stop live simulator sessions. Recorded permission boundary: Remote Mac build/test/run/archive authority over uploaded project.

What data-handling boundary should I consider?

Workspace files are uploaded content-addressed to the doublespeed Mac fleet; changed files are re-uploaded on later jobs. Recorded sensitive-access context: Source code; Build artifacts; Potential embedded project secrets.

What limitations and risks should I check before use?

Remote build service receives source; API key and workspace boundaries must be controlled. Most operations require DS_API_KEY and consume Mac time. Only files under workspaceRoot are uploaded, but source code still leaves local machine. Code signing/TestFlight and screenshot/accessibility capture are not yet supported. Live simulator URL is intended for human inspection. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.