Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/elfensky/macos-apps-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/elfensky/macos-apps-mcp/macos-apps)<a href="https://agentmods.dev/mcp/elfensky/macos-apps-mcp/macos-apps"><img src="https://agentmods.dev/badge/mcp/elfensky/macos-apps-mcp/macos-apps/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/elfensky/macos-apps-mcp/macos-apps"><img src="https://agentmods.dev/badge/mcp/elfensky/macos-apps-mcp/macos-apps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
macos-apps scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"macos-apps": {
"command": "uvx",
"args": [
"macos-apps-mcp"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 8 lines scan A fca0014f5bcd
macos-apps is an MCP server published in the GitHub repository elfensky/macos-apps-mcp (1 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.
Other mcp servers, from other repositories
apple-productivity-mcp
On-demand local Apple Mail, Calendar, and Reminders MCP server for macOS. Runs locally from the @gambadio/apple-productivity-mcp npm package.
apple-tools-mcp
Unified Apple ecosystem MCP server for macOS. Runs locally from the apple-tools-mcp Python package. Needs 12 environment variables to run.
apple-calendar-mcp
Local Apple Calendar server for macOS. Runs locally from the apple-calendar-mcp Python package. Needs 3 environment variables to run.
apple-mcp-mail
Local MCP server for Apple Mail on macOS. Runs locally from the apple-mcp-mail Python package. Needs 3 environment variables to run.
apple-mcp-reminders
Local Apple Reminders MCP server for macOS. Runs locally from the apple-mcp-reminders Python package. Needs 2 environment variables to run.
macuse
MCP server "macuse" as configured in macuse-app/macuse-mcp. Launched with https://github.com/macuse-app/macuse-mcp/releases/download/v1.3.0/macuse-1.3.0.m.