omnifocus-mcp@1.17.1
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server that integrates with OmniFocus for AI assistant interaction" 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso omnigroup.com, omni-automation.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- 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.
What changed since 1.17.0
vet-skills diff omnifocus-mcp 1.17.0 1.17.1In the sandbox, this version reached for nothing 1.17.0 did not. Compared from the two recorded runs, not from source.
1.17.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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-21 and scored it 90/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 · 6 s · 2 scenarios · 0 deviationsStatic findings
// nothing at all — every osascript we send and then kill leaves a permanentlyFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* Signal/EOF propagation through the npx → cli.cjs → node wrapper chain isFix: Pin versions and sources; vendor anything fetched at install time.// A client-kill means the app never answered. Do not retry it — trip theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."build": "tsc && npm run copy-files && chmod 755 dist/server.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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
Not checked against OSV yet; the weekly check has not reached this version.