pyapple-mcp@1.6.1
CAUTION· not startedPublisher claims: "MCP server and command-line tool for macOS: Messages, Mail, Notes, Calendar, Reminders, Contacts, Maps and Shortcuts" 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
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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: Caution 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso apple.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; References a credential file in the home directory; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 3 scenarios · 0 deviationsStatic findings
done = subprocess.run([str(fake)], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.completed = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.completed = subprocess.run(argv, capture_output=True, text=True, timeout=15, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.**`--body "$(cat draft.txt)"` was the only way to send a real email throughFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.process = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Reading goes through `chat.db` directly; sending goes through AppleScript.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.# to text `~/.ssh/id_rsa` to a number in the message body — and every step ofFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# to text `~/.ssh/id_rsa` to a number in the message body — and every step ofFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# `.gnupg`, `.config`, `.env`, `.git`. Nobody means to text a dotfile,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.can be told *by that mail* to text `~/.ssh/id_rsa` to a number in the body,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.can be told *by that mail* to text `~/.ssh/id_rsa` to a number in the body,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.No real script here: the kill is faked, because what is being asserted isFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`~/Desktop/holiday.jpg -> ~/.ssh/id_rsa` is judged as `~/.ssh/id_rsa`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`~/Desktop/holiday.jpg -> ~/.ssh/id_rsa` is judged as `~/.ssh/id_rsa`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.caller: `mark_as_read` must not turn the kill back into a failure report.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(["osascript", "-e", script], capture_output=True, text=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.completed = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 pyapple-mcp@1.6.1 as of 34 min ago. This is the package itself, not its dependencies.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim 54yyyu: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.