MCP servers › io.github.hridaya423 › phonedriver
MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19
phonedriver MCP server
Registry name io.github.hridaya423/phonedriver
by hridaya423 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
MCP server and CLI that lets AI agents see and control Android phones and iPhones (iOS) as text. — the publisher's description
Summary
io.github.hridaya423/phonedriver is a local MCP server listed in the official MCP registry at version 0.1.5, under the namespace of the GitHub account hridaya423. Its linked repository, github.com/hridaya423/phonedriver, belongs to the same GitHub account.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #1,873 of 20,610 packages by monthly downloads, tied with 1 other
- #709 of 28,859 repositories by GitHub stars, tied with 3 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- npm · listed version current
- License
- AGPL-3.0-only
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.1.5, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-10 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 6 versions listed, 2026-11-10 to 2026-11-18; 6 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 6 versions
0.1.5· 2026-11-180.1.4· 2026-11-140.1.3· 2026-11-130.1.2· 2026-11-120.1.1· 2026-11-100.1.0· 2026-11-10
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.4 (published 2026-11-14) → 0.1.5 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher’s GitHub release note for v0.1.5 (“0.1.5”), published 2026-11-17.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
## Release Notes Released 17 November 2026. - **`phonedriver init`** adds phonedriver to the agents installed on this machine (Claude Code, Codex, Cursor, VS Code and Gemini CLI) and then runs the doctor checks. - **`phonedriver boot <name>`** starts an iOS Simulator or an Android virtual device that is off and waits until it has booted. With nothing connected, the error names what can be started. - **Saved runs**: `phonedriver save run.steps` writes what the session did, and `phonedriver replay run.steps` does it again with no model. It stops at the first step that fails and shows the screen. - **A GitHub Action**: `uses: hridaya423/phonedriver@v0.1.5` starts an Android emulator or an iOS Simulator, installs your app and replays saved runs on every commit. Each run is a row in the job summary, and its reply, the screen where it stopped and a video go in an artifact. - **Screen checks in a replay**: `replay run.steps --screens screens/run` keeps a screenshot after each step the first time, and later stops at the first step whose screen shows different text, with the text that changed (`~ "General" → "About"`). The status bar is left out, with its clock, notification icons and battery, and a screen still moving is looked at again until it stops, so an animation or a notification does not fail a job. The Action takes the folder as `screens`. - **`phonedriver page`** prints the web page in front as text, whole, without scrolling. On Android, it works in Chrome and in the web views of debug builds. - **`phonedriver record start` and `record stop`** save an MP4 of the screen on Android and on the iOS Simulator, with a file of the actions done during it. - **Settings by key on Android 17**: `phonedriver setting find`, `get` and `set` change a setting without opening its screen. - **App permissions**: `phonedriver apps grant <app> <permission>` and `revoke` work without launching the app. - **Crashes**: an action during which the app crashed says so in its reply, and `phonedriver logs` prints the app's last lines and its last crash. - **Several agents on one Android phone**: a device id that ends in `+a`, `+b` and so on gives each agent a hidden screen of its own (Android 13 and later). - **An Android phone in use stays awake**: while phonedriver has used a phone in the last 10 minutes it resets the phone's screen timeout every 10 seconds, on the phone's own screen and with `PHONEDRIVER_DISPLAY=hidden`, so the phone no longer locks while an agent thinks. The screen still dims on its usual schedule. `phonedriver release` stops it. Tested on a HONOR X8 and the emulator. - **The emulator's console**: on an Android emulator, `phonedriver shell "emu geo fix -122.41 37.77"` sets the location, and any other console command works the same way (`emu sms send`, `emu power capacity`). On the iOS Simulator, `shell "simctl location set 37.77,-122.41"` does it. - **Fingerprint and Face ID**: `press fingerprint` and `press wrong-fingerprint` on an Android emulator and on an iOS Simulator. - **`press landscape` and `press portrait`** turn the screen. - **Accessibility audit**: `phonedriver snapshot --audit` (MCP: `audit: true`) adds the screen's controls that have no name a screen reader can say and its tap targets under 44 by 44 points on iOS or 48 by 48 on Android. - **`phonedriver compare a.png b.png`** says in text what changed between two screenshots, in 0.3 to 1.2 s on a Mac. The status bar's clock is left out. - **Screens with no element list** are read from the screenshot on Windows hosts too, and on Linux hosts with Tesseract installed (the `tesseract-ocr` package), not only on a Mac. - **Reading a screenshot on a Mac starts at once**: the first read in a process used to wait 21 to 31 s while macOS built the model for Vision's Accurate level, and on some Macs that level failed after 12 to 17 s every time. phonedriver now reads at Vision's Fast level, which needs no such model: about 20 ms a screen on an M4 Pro. - **An iPhone's signature r
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package phonedriver
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"phonedriver": {
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"phonedriver": {
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"phonedriver": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"phonedriver","type":"stdio","command":"npx","args":["-y","phonedriver@0.1.5","mcp"]}'Claude Code
claude mcp add --transport stdio phonedriver -- npx -y phonedriver@0.1.5 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"phonedriver": {
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"phonedriver": {
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.phonedriver] command = "npx" args = ["-y", "phonedriver@0.1.5", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"phonedriver": {
"command": "npx",
"args": [
"-y",
"phonedriver@0.1.5",
"mcp"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y phonedriver@0.1.5 mcp
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.5
- Latest stable
- 0.1.5
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-19 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-6QhNwNkPICla5HMi6…
- Signature
- signed
- License
- AGPL-3.0-only
Source: the package registry · 2026-11-19.
Usage
- Downloads
- 1,832 in the last month
Source: api.npmjs.org · 2026-11-19.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.1.5). Source: registry.npmjs.org/phonedriver/0.1.5 · read 2026-11-19.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/phonedriver/0.1.5 · read 2026-11-19.
- Node.js version (npm). Needs Node 18 or later (engines.node
>=18). Source: registry.npmjs.org/phonedriver/0.1.5 · read 2026-11-19. - MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: registry.npmjs.org/phonedriver/-/phonedriver-0.1.5.tgz · read 2026-11-19. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/phonedriver/0.1.5 · read 2026-11-19.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://phonedriver.dev/.well-known/ (HTTP 404, 2026-11-19). Source: phonedriver.dev/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://phonedriver.dev/.well-known/ (HTTP 404, 2026-11-19). Source: phonedriver.dev/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.1.5 on npm | Exists and can be installed | matches | npm · 2026-11-19 |
| Repository github.com/hridaya423/phonedriver | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.hridaya423
- GitHub owner
- a personal account (hridaya423)
- Build record
- signed
- Repository
- github.com/hridaya423/phonedriver
- Stars
- 179
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-12.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #1,873 of 20,610 packages by monthly downloads, tied with 1 other
- #709 of 28,859 repositories by GitHub stars, tied with 3 others
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierAGPL-3.0-only
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.hridaya423/phonedriver
Answered from the data aboveWho publishes io.github.hridaya423/phonedriver?
The registry ties the namespace io.github.hridaya423 to the GitHub account hridaya423; only its owner can publish under it. Its linked repository, github.com/hridaya423/phonedriver, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.hridaya423/phonedriver safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.hridaya423/phonedriver been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.hridaya423/phonedriver publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.1.5, the latest stable release on npm.
Where is the source code of io.github.hridaya423/phonedriver?
In github.com/hridaya423/phonedriver, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.hridaya423/phonedriver: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.hridaya423/phonedriver
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.hridaya423/phonedriver)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology