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/vitalops/opendeskWrote 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/vitalops/opendesk/opendesk-opendesk)<a href="https://agentmods.dev/mcp/vitalops/opendesk/opendesk-opendesk"><img src="https://agentmods.dev/badge/mcp/vitalops/opendesk/opendesk-opendesk/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/vitalops/opendesk/opendesk-opendesk"><img src="https://agentmods.dev/badge/mcp/vitalops/opendesk/opendesk-opendesk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
opendesk 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 today.
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
{
"opendesk": {
"command": "uvx",
"args": [
"--from",
"opendesk==0.3.0",
"opendesk-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.
- today First seen · 10 lines scan A 768d3d17c6d0
opendesk is an MCP server published in the GitHub repository vitalops/opendesk (88 stars, last pushed today), 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-20.
Other mcp servers, from other repositories
hunch
Drive your Mac focus-free over MCP: OS APIs, AppleScript, CDP, and Accessibility. Runs locally from the hunch-sdk Python package.
parallel-browser-mcp
MCP server for parallel browser automation across multiple providers. Runs locally from the parallel-browser-mcp npm package. Needs 7 environment variables to run.
outlook-web-mcp-server
MCP server "outlook-web-mcp-server" as configured in ma-nakaya/outlook-web-mcp-server. Runs locally from the outlook-web-mcp-server Python package.
mcp
Build, run, inspect, and publish browser extensions from any MCP client. 31 tools, 11 browsers. Runs locally from the @extension.dev/mcp npm package.
radmail-mcp
RadMail MCP server — email operating system for agents: two-axis triage (importance x urgency), a 'Right Now' lane, commitment follow-through, reviewable drafts, and a machine-verifiable BEC hard-stop (money / changed-banking / first-contact / decision /. Runs locally from the radmail-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.