Skills/npm/omnifocus-mcp

omnifocus-mcp@1.17.1

VERIFIED· not started

Publisher 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.

Registry npm (MCP server)Publisher themotionmachine · publishing for 595 daysInstalls 1,792Last detonated 11 min ago
$claude mcp add omnifocus-mcp -- npx -y omnifocus-mcp
WatchReport an issue

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.

$vet-skills run --net declared -- npx -y omnifocus-mcp

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.1

In 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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.2sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-i1htWu/task/home/.npm/_logs/2026-11-21T20_37_30_346Z-debug-0.log
6.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
6.2sprocessscript backend runs setup only
6.2sprocessno install scripts to re-run

Static findings

MEDIUM
Process kill commanddist/utils/scriptExecution.js:167 · Process kill command — agent can terminate processes// 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.
AST05
MEDIUM
npx invocation of non-well-known packagedist/utils/idleTimeout.js:4 · npx invocation of non-well-known package — may execute untrusted code* Signal/EOF propagation through the npx → cli.cjs → node wrapper chain isFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Process kill commanddist/utils/scriptExecution.js:183 · Process kill command — agent can terminate processes// 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.
AST05
MEDIUM
File permission modification commandpackage.json:15 · File permission modification command — agent changes file ownership/permissions"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.
AST05

Cost to the agent

Instructions loaded
≈61 tok
1 file · 67 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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.