Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Karagöz

NPM · KARAGOZ-MCP

Device automation for Android emulators and phones, iOS simulators and iPhones. No daemon.

Available components

+4 this week 83 Trust /100

Last scanned (3 hours ago)

Scores higher than 77% of npm servers

Category IoT and Hardware

Trust breakdown (7 categories)

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to yagizdo/karagoz-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1604 tokens (~89/item across 18 items; 18 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% 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
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 19 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
Changelog

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.

  • 5 Nov 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.

  • 4 Nov 26 0
    • Stability: 0.23 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.2 → 0.4.0 functional
  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.1 → 0.3.2 functional
  • 1 Nov 26 +16
    • Stability: 0.13 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.0 → 0.3.1 functional
  • 31 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Schema quality: 79 → 89 ▼ functional
    • Package version: 0.2.0 → 0.3.0 functional
  • 30 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.1.1 → 0.2.0 functional
  • 29 Oct 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
Diagnostics

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 5 Nov 2026 · Analysed npm/karagoz-mcp@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo yagizdo/karagoz-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/yagizdo/karagoz-mcp/.github/workflows/release.yml@refs/tags/v0.4.0
Rekor log index 3689067744
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:da489a346696d5799213df1633538e1ecfbf7ba4cb59326be08d99ea54d6eaefd8939cc2b4f4d2f7402974a383f741d59dae5e091c26663aeed910c3b

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~1,508 tokens

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 →

Tool Tokens
devices ~28

List Android devices and emulators, running iOS simulators, and iPhones connected to this Mac.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doctor ~35

Report which adb and Xcode tools karagoz uses, their versions, and how to fix one that is missing, old or broken.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

double_tap ~164

Double-tap x, y in physical pixels, or the center of the node whose text or contentDesc (iOS: label or value) equals text, or whose resource id (iOS: identifier) matches id. An iPhone needs install_runner once.

NameTypeReqDescription
devicestring–Id or name.
idstring–Resource id, full or the part after :id/ (iOS: identifier).
textstring–Exact text or contentDesc (iOS: label or value), case-sensitive.
timeoutinteger–With text or id: ms to keep reading the tree until the node appears; the call can run up to 6 s longer.
xnumber––
ynumber––

No output schema declared.

No examples provided.

install ~99

Install an .apk, or a .app or .ipa on an iOS simulator or iPhone, or replace the installed version of the same app. An iPhone takes only a build signed for it; karagoz does not re-sign. Times out after 30 s plus 1 s per MB.

NameTypeReqDescription
apkstringyesAbsolute path to the .apk, .app or .ipa.
devicestring–Id or name.

No output schema declared.

No examples provided.

install_runner ~71

Build karagoz's runner with your Apple team and install it on a paired iPhone over USB; ui_tree, tap, swipe, text and key need it there.

NameTypeReqDescription
devicestring–Id or name.
teamstring–Apple team ID; needed only when Xcode lists several.

No output schema declared.

No examples provided.

key ~96

Press one key.

NameTypeReqDescription
devicestring–Id or name.
keystringyesKeyEvent name (HOME, BACK, KEYCODE_7) or code 1-340; "7" is code 7 (KEYCODE_0), not the digit. iOS takes HOME, POWER, VOLUME_UP/DOWN and keyboard keys; an iPhone only keys that type a character, and…

No output schema declared.

No examples provided.

launch ~45

Start an app as its launcher icon does. On iOS it returns before the app is in front.

NameTypeReqDescription
devicestring–Id or name.
packagestringyes–

No output schema declared.

No examples provided.

logs ~106

Read the newest device log records, oldest first. On iOS without since: the last minute, or the last hour with package. An iPhone read takes about 10 s.

NameTypeReqDescription
devicestring–Id or name.
linesinteger–Number of newest records. Default 30.
packagestring–Only this app's records.
sincenumber–Unix seconds on the device clock; only later records. Pass a record's time to continue.

No output schema declared.

No examples provided.

long_press ~179

Long-press x, y in physical pixels, or the center of the node whose text or contentDesc (iOS: label or value) equals text, or whose resource id (iOS: identifier) matches id. An iPhone needs install_runner once.

NameTypeReqDescription
devicestring–Id or name.
durationinteger–Hold time in ms. Default 1000.
idstring–Resource id, full or the part after :id/ (iOS: identifier).
textstring–Exact text or contentDesc (iOS: label or value), case-sensitive.
timeoutinteger–With text or id: ms to keep reading the tree until the node appears; the call can run up to 6 s longer.
xnumber––
ynumber––

No output schema declared.

No examples provided.

open_url ~88

Open a URL in the app that handles it, or in the app named by app. On iOS it returns before the app is in front, and a simulator may first ask "Open in <app>?".

NameTypeReqDescription
appstring–Package name or bundle id; not on an iOS simulator.
devicestring–Id or name.
urlstringyes–

No output schema declared.

No examples provided.

screenshot ~97

Save a full-resolution PNG of the screen and return its path with size, scale and safe area. Use ui_tree to read the screen; inline only to look at the image.

NameTypeReqDescription
devicestring–Id or name.
inlineboolean–Also return the image. Take coordinates from ui_tree, not from the image.
outstring–Absolute PNG path, ending in .png. Default: a new temp file.

No output schema declared.

No examples provided.

swipe ~90

Swipe from x1, y1 to x2, y2 in physical pixels. An iPhone needs install_runner once.

NameTypeReqDescription
devicestring–Id or name.
durationinteger–ms from start to end. Default 300.
x1numberyes–
x2numberyes–
y1numberyes–
y2numberyes–

No output schema declared.

No examples provided.

tap ~160

Tap x, y in physical pixels, or the center of the node whose text or contentDesc (iOS: label or value) equals text, or whose resource id (iOS: identifier) matches id. An iPhone needs install_runner once.

NameTypeReqDescription
devicestring–Id or name.
idstring–Resource id, full or the part after :id/ (iOS: identifier).
textstring–Exact text or contentDesc (iOS: label or value), case-sensitive.
timeoutinteger–With text or id: ms to keep reading the tree until the node appears; the call can run up to 6 s longer.
xnumber––
ynumber––

No output schema declared.

No examples provided.

terminate ~32

Force-stop every process of an app.

NameTypeReqDescription
devicestring–Id or name.
packagestringyes–

No output schema declared.

No examples provided.

text ~59

Type into the focused field. Any text; on Android, text beyond ASCII is pasted through the clipboard and the old clip put back. An iPhone needs install_runner once.

NameTypeReqDescription
devicestring–Id or name.
textstringyes–

No output schema declared.

No examples provided.

ui_tree ~98

Return the focused window's accessibility tree as JSON, compact by default: nodes with no text, label or action and nodes off screen are left out. Node bounds [left, top, right, bottom] are the physical pixels tap and swipe take. On an iPhone it needs karagoz's runner: install it once with install_runner.

NameTypeReqDescription
detailstring–full: every node.
devicestring–Id or name.

No output schema declared.

No examples provided.

uninstall ~28

Remove an app.

NameTypeReqDescription
devicestring–Id or name.
packagestringyes–

No output schema declared.

No examples provided.

uninstall_runner ~33

Remove karagoz's runner and its provisioning profile from an iPhone.

NameTypeReqDescription
devicestring–Id or name.

No output schema declared.

No examples provided.

Install

How do I install the Karagöz MCP server?

Karagöz runs locally as an npm package, launched with npx -y karagoz-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 · karagoz-mcp

# add to Claude Code
claude mcp add yagizdo-karagoz-mcp -- npx -y karagoz-mcp
Common questions

What is the Karagöz MCP server?

Karagöz is an MCP server listed in the public MCP registry as io.github.yagizdo/karagoz-mcp. Device automation for Android emulators and phones, iOS simulators and iPhones. No daemon. This page covers its npm package (karagoz-mcp).

Is the Karagöz MCP server safe to use?

Karagöz scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Karagöz MCP server expose?

Karagöz exposes 18 tools: devices, screenshot, ui_tree, tap, long_press, and 13 more. Their descriptions and schemas cost roughly 1,508 tokens of context every time the server is loaded.

Is the Karagöz MCP server still maintained?

Karagöz is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Karagöz MCP server under?

Karagöz declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.