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/cyanheads/macos-mcp-serverWrote 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/cyanheads/macos-mcp-server/macos-mcp-server)<a href="https://agentmods.dev/mcp/cyanheads/macos-mcp-server/macos-mcp-server"><img src="https://agentmods.dev/badge/mcp/cyanheads/macos-mcp-server/macos-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
macos-mcp-server 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 8d 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-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/macos-mcp-server"
],
"env": {
"MACOS_SCREENSHOT_DIR": "",
"MACOS_DISPLAY_LAYOUTS": "{}",
"MCP_LOG_LEVEL": "info"
}
}
}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.
- 8d ago First seen · 14 lines scan A b21430724643
macos-mcp-server is an MCP server published in the GitHub repository cyanheads/macos-mcp-server (2 stars, last pushed 16d ago), licensed Apache-2.0. 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-08-31.
Other mcp servers, from other repositories
macbeth
MCP server "macbeth" as configured in wende/macbeth. Runs client/dist/mcp.js with node.
openchargemap-mcp-server
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map. Runs locally from the @cyanheads/openchargemap-mcp-server npm package. Needs 4 environment variables to run.
iac-mcp
MCP server "iac-mcp" as configured in jsavin/iac-mcp. Runs /absolute/path/to/iac-mcp/dist/index.js with node. Needs 1 environment variable to run.
directory
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers. Remote server at skills.911fund.io.
mcp-office-excel
Local-first MCP servers for Microsoft Office — Excel, PowerPoint, and Word automation via the Model Context Protocol. Runs on Windows. Runs locally from the mcp-office Python package. Needs 4 environment variables to run.
oecd-mcp-server
Search and query 1,500+ OECD statistical datasets via SDMX. Keyless. Runs locally from the @cyanheads/oecd-mcp-server npm package. Needs 1 environment variable to run.