Atlas / MCP servers / atom2ueki / Ios Simulator

Ios SimulatorSAFE

mcp/atom2ueki/ios-simulator-1

Model Context Protocol (MCP) implementation for iOS simulators

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
12 8r · 2w · 2d
Transport
stdio
License
MIT
Stars
44
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://smithery.ai/server/@atom2ueki/mcp-server-ios-simulator)

A server that implements the Model Context Protocol (MCP) for iOS simulators, built on top of appium-ios-simulator and utilizing the MCP TypeScript SDK.

📋 Overview

This project provides a bridge between iOS simulators and the Model Context Protocol, allowing for standardized communication with iOS simulator instances. It enables programmatic control of iOS simulators while leveraging the MCP protocol for consistent interfaces across different environments. The server utilizes stdio as its transport mechanism, making it ideal for integration with Claude Desktop and other MCP-compatible clients.

🎬 Demo

Demo showing how to boot an iOS simulator using Claude AI Desktop

🏗️ Architecture

The server consists of three main components:

  1. 🔄 Simulator Management Layer - Handles iOS simulator lifecycle and interactions
  2. 🔌 MCP Protocol Implementation - Implements the Model Context Protocol using the TypeScript SDK with stdio transport
  3. 📊 Logger Component - Provides file-based logging without interfering with the stdio transport
┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│  MCP Protocol   │     │     Stdio       │     │    Simulator    │
│  Implementation │◄────┤    Transport    │◄────┤   Management    │
│                 │     │                 │     │      Layer      │
└─────────────────┘     └─────────────────┘     └─────────────────┘
▲                 
Read from source at commit 5bf1ba5e8605OBSERVED · 2026-10-08
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add mcp-server-ios-simulator -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "mcp-server-ios-simulator": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (12)

8 read · 2 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.

ToolRiskDescription
boot-simulator-by-udidread
create-simulator-sessionwrite
install-appwrite
launch-appread
list-available-simulatorsread
list-booted-simulatorsread
list-simulator-sessionsread
shutdown-simulatorread
shutdown-simulator-by-udidread
tapread
terminate-appdestructive
terminate-simulator-sessiondestructive
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfaceWARN
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (3)

MEDIUMFilesystem / path · mcp.destructive_tools · CWE-22, CWE-59
terminate-app, terminate-simulator-session
Why it matters. 2 tool(s) can delete or overwrite
Fix. prefer a read-only mode or scoped tokens; the page states the blast radius
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
appium-ios-simulator, express, body-parser, cors, winston, uuid, @modelcontextprotocol/sdk, dotenv
Why it matters. 20 dependency range(s) float
Fix. pin exact versions or ship a lockfile
INFOInventory / provenance · inv.oversize · CWE-1104
demo/demo1.gif
demo/demo1.gif
Why it matters. 9900469 bytes not read

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha 5bf1ba5e8605full audit observations/trust-audit/mcp-server/atom2ueki__ios-simulator-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-085bf1ba5e8605SAFEB89first audit
06

Questions

What is the Ios Simulator MCP server?

Model Context Protocol (MCP) implementation for iOS simulators

What tools does Ios Simulator expose?

12 in total: 8 read-only, 2 that write, and 2 that can delete or overwrite (terminate-app, terminate-simulator-session). Every one is listed on this page with its risk.

Is Ios Simulator safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.

What credentials does Ios Simulator need?

No credential environment variables were found in its source, so it appears to need none.

How does Ios Simulator run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as mcp-server-ios-simulator at 0.1.0.

How current is this page?

The grade is for one exact copy of the source (5bf1ba5e8605), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement