Omnifocus (IllyaStarikov) MCP Server

omnifocus-mcp-server npm v1.2.0 Source verified

Published by illyastarikov — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for OmniFocus via Omni Automation API

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/omnifocus/executor.js)MTC-SRC-002

In the server's implementation (`dist/omnifocus/executor.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { config } from "../config.js"; im

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/omnifocus/executor.js

Tools 51

Each tool and what it can reach — statically extracted from the published source.

  • dump_databasereads sensitive data
  • add_task_notificationno sensitive capability
  • append_task_noteno sensitive capability
  • batch_complete_tasksno sensitive capability
  • batch_create_tasksno sensitive capability
  • batch_delete_tasksno sensitive capability
  • complete_projectno sensitive capability
  • complete_taskno sensitive capability
  • convert_task_to_projectno sensitive capability
  • create_folderno sensitive capability
Show 41 more tools ↓
  • create_projectno sensitive capability
  • create_tagno sensitive capability
  • create_taskno sensitive capability
  • delete_folderno sensitive capability
  • delete_projectno sensitive capability
  • delete_tagno sensitive capability
  • delete_taskno sensitive capability
  • drop_projectno sensitive capability
  • drop_taskno sensitive capability
  • duplicate_tasksno sensitive capability
  • get_database_summaryno sensitive capability
  • get_flagged_tasksno sensitive capability
  • get_folderno sensitive capability
  • get_inbox_tasksno sensitive capability
  • get_perspective_tasksno sensitive capability
  • get_projectno sensitive capability
  • get_project_tasksno sensitive capability
  • get_review_queueno sensitive capability
  • get_tagno sensitive capability
  • get_taskno sensitive capability
  • get_task_countno sensitive capability
  • get_today_completed_tasksno sensitive capability
  • list_foldersno sensitive capability
  • list_perspectivesno sensitive capability
  • list_projectsno sensitive capability
  • list_tagsno sensitive capability
  • list_task_notificationsno sensitive capability
  • list_tasksno sensitive capability
  • mark_reviewedno sensitive capability
  • move_projectno sensitive capability
  • move_tasksno sensitive capability
  • remove_task_notificationno sensitive capability
  • save_databaseno sensitive capability
  • searchno sensitive capability
  • set_task_tagsno sensitive capability
  • sync_databaseno sensitive capability
  • uncomplete_taskno sensitive capability
  • update_folderno sensitive capability
  • update_projectno sensitive capability
  • update_tagno sensitive capability
  • update_taskno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.2.0 latest A 94/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/omnifocus-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/omnifocus-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/omnifocus-mcp-server"><img src="https://mcptrustchecker.com/registry/omnifocus-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/omnifocus-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan omnifocus-mcp-server --online

Use the free API → How scoring works

Other implementations of Omnifocus 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Productivity & Workflow