Atlas / MCP servers / turlockmike / Apple Notifier

Apple NotifierSAFE

mcp/turlockmike/apple-notifier
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
7 6r · 1w · 0d
Transport
stdio
License
MIT
Stars
26
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://mseep.ai/app/turlockmike-apple-notifier-mcp)

[](https://smithery.ai/server/apple-notifier-mcp) Send native macOS notifications and interact with system dialogs through any MCP-compatible client like Claude Desktop or Cline.

Prerequisites

  • macOS
  • Node.js >= 18
  • An MCP-compatible client (Claude Desktop, Cline)

Troubleshooting: Notifications Not Appearing

For notifications to display, the terminal or application running the MCP server needs notification permissions in macOS.

Grant Notification Permissions

  1. For Claude Desktop users:
  2. Open System Preferences (or System Settings on macOS Ventura+)
  3. Go to Notifications
  4. Find Node or terminal-notifier (whichever appears)
  5. Enable Allow Notifications
  6. Set alert style to Banners or Alerts
  1. For Claude Code / Terminal users:
  2. Open System Preferences > Notifications
  3. Find Terminal (or iTerm if using iTerm2)
  4. Enable Allow Notifications
  1. If the app doesn't appear in Notifications settings:
  2. Run a test notification manually in Terminal:
osascript -e 'display notification "Test" with title "Hello"'
  • This should trigger macOS to prompt for or register notification permissions
  • Then check System Preferences again
  1. Check Focus Mode / Do Not Disturb:
  2. Ensure Focus Mode or Do Not Disturb is not enabled
  3. Check the Control Center in the menu bar

Verify Notifications Work

Test from terminal before using via MCP:

osascript -e 'display notification "Test message" with title "Test tit
Read from source at commit dd2720473dedOBSERVED · 2026-10-09
Advertisement
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add apple-notifier-mcp -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "apple-notifier-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (7)

6 read · 1 write · 0 destructive.

ToolRiskDescription
prompt_userreadDisplay a dialog prompt to get user input
select_filereadOpen native file picker dialog
select_fileEvalreadEvaluates the behavior of the select_file tool by verifying its ability to open a file dialog with specified parameters
send_notificationwriteSend a notification on macOS using osascript
speakreadSpeak text using macOS text-to-speech
speakEvalreadEvaluates the macOS text-to-speech speak tool
take_screenshotreadEvaluates the take_screenshot tool functionality
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, mcp-evals, @types/node, typescript
Why it matters. 4 dependency range(s) float
Fix. pin exact versions or ship a lockfile
INFOPrompt injection · prompt.credential_read · CWE-94, CWE-1427
README.md:197
The evals package loads an mcp client that then runs the index.ts file, so there is no need to rebuild between tests. You can load environment variables by prefixing the npx command. Full documentatio
Why it matters. asks the agent to read credentials

Gates applied: no_behavioural_pass.

Audited 2026-10-09 · audit v0.4.1 · source sha dd2720473dedfull audit observations/trust-audit/mcp-server/turlockmike__apple-notifier.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-09dd2720473dedSAFEB89first audit
06

Questions

What tools does Apple Notifier expose?

7 in total: 6 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Apple Notifier safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Apple Notifier need?

No credential environment variables were found in its source, so it appears to need none.

How does Apple Notifier run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as apple-notifier-mcp at 1.1.0.

How current is this page?

The grade is for one exact copy of the source (dd2720473ded), read on 2026-10-09. The repository is watched and re-audited when it changes.

Advertisement