phone-harness-mcp@0.1.0
VERIFIED· not startedPublisher claims: "Connect AI agents to real iPhones and Androids" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
PHONE_HARNESS_API_KEYPHONE_HARNESS_CLOUD_OAUTH_CLIENT_IDPHONE_HARNESS_CLOUD_OAUTH_ISSUERor--oauth-issuerConfiguration, not credentials: PHONE_HARNESS_CLOUD_API, PHONE_HARNESS_HOME- Where it talks to
- phone-harness.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for PHONE_HARNESS_API_KEY, PHONE_HARNESS_CLOUD_OAUTH_CLIENT_ID, PHONE_HARNESS_CLOUD_OAUTH_ISSUER and talks to phone-harness.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>Copilot CLI</b></summary> Run `/mcp add`, or put this in `~/.copilot/mcp-config.json`: ```json { "mcpServers": { "phone-harness": { "type": "local",Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Desktop</b></summary> Settings → Connectors → Add custom connector, URL `https://mcp.phone-harness.com/mcp`. Or add the standard config to `cFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for phone-harness-mcp@0.1.0 as of 2 h ago. This is the package itself, not its dependencies.