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/trsdn/mcp-server-uiautomationWrote 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/trsdn/mcp-server-uiautomation/uia-mcp)<a href="https://agentmods.dev/mcp/trsdn/mcp-server-uiautomation/uia-mcp"><img src="https://agentmods.dev/badge/mcp/trsdn/mcp-server-uiautomation/uia-mcp/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/trsdn/mcp-server-uiautomation/uia-mcp"><img src="https://agentmods.dev/badge/mcp/trsdn/mcp-server-uiautomation/uia-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
uia-mcp 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
{
"uia-mcp": {
"type": "stdio",
"command": "${workspaceFolder}/src/UIAutomationMcp.McpServer/bin/Release/net9.0-windows/UIAutomationMcp.McpServer.exe"
}
}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 · 6 lines scan A 5709ea141c34
uia-mcp is an MCP server published in the GitHub repository trsdn/mcp-server-uiautomation (2 stars, last pushed yesterday), 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-12.
Other mcp servers, from other repositories
agent-computer-use-mcp
A local MCP server for Gateway-managed computer use with cua-driver, OCR, and user-only desktop overlays. Runs locally from the agent-computer-use-mcp npm package.
core
Agent-native MCP server for driving, inspecting, and asserting on real Electron desktop apps. Runs locally from the @electron-stagewright/core npm package.
realhands
MCP server that lets Claude operate the REAL desktop (mouse, keyboard, screen) like a human — works in your own logged-in Chrome and any app. Runs locally from the realhands Python package.
mac-use-mcp
Zero-dependency macOS desktop automation for AI agents. 18 tools via MCP. macOS 13+. Runs locally from the mac-use-mcp npm package.
electron-driver
MCP server that lets AI agents drive Electron apps — click, type, drag, screenshot, eval JS in the renderer or main process, capture console logs, handle multi-window apps, and more. Runs locally from the electron-driver npm package.
sassymcp
Unified MCP server for cross-platform (Windows/macOS/Linux) desktop automation, Android device control, security auditing, web inspection, cross-session communication, GitHub operations, and AI workflow persona. Runs locally from the sassymcp Python package.