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/rcobb2/desktop-management-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/rcobb2/desktop-management-mcp/jamf-remote)<a href="https://agentmods.dev/mcp/rcobb2/desktop-management-mcp/jamf-remote"><img src="https://agentmods.dev/badge/mcp/rcobb2/desktop-management-mcp/jamf-remote.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jamf-remote 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 7d 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
{
"jamf-remote": {
"type": "stdio",
"command": "${CLAUDE_PROJECT_DIR:-.}/scripts/mcp-wrappers/jamf-mcp-device.sh",
"args": []
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 7 lines scan A d5e17b974021
jamf-remote is an MCP server published in the GitHub repository rcobb2/desktop-management-mcp (0 stars, last pushed 3d 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-09-01.
Other mcp servers, from other repositories
Windows-MCP
Lightweight MCP Server for interacting with Windows Operating System. Runs locally from the windows-mcp Python package.
kip-mcp-server
Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards. Runs locally from the kip-mcp-server npm package. Needs 7 environment variables to run.
obsbot-mcp
Control an OBSBOT Tiny 2 camera: pan/tilt/zoom, AI tracking, focus, exposure, snapshots, recording. Runs locally from the obsbot-mcp npm package. Needs 1 environment variable to run.
netmiko-mcp-server
MCP server "netmiko-mcp-server" as configured in nagayon-935/netmiko-mcp-server. Runs locally from the netmiko-mcp-server Python package.
cadloop-slicer
Parametric CAD and slicing behind MCP, with every plate proven on the bed. Runs locally from the cadloop Python package. Needs 4 environment variables to run.
mijia
MCP server "mijia" as configured in oadank/miot-mcp. Launched with C:\D\opt\miot-mcp\venv\Scripts\python.exe C:\D\opt\miot-mcp\mcp_server\mcp_serve. Needs 3 environment variables to run.