{"id":"dddabtc-winremote-mcp","name":"winremote-mcp","af_score":61.0,"security_score":61.0,"reliability_score":32.5,"what_it_does":"winremote-mcp runs a Windows “Model Context Protocol” (MCP) server on a Windows machine to enable remote desktop automation and administration for MCP-capable agents/clients (e.g., Claude Desktop, OpenClaw). It provides tools for screenshots, GUI input automation, PowerShell/shell command execution, file operations, system/process management, OCR, and screen recording. It supports API-key bearer auth, IP allowlisting, TLS, and an embedded OAuth 2.0 authorization server.","best_when":"Used on a Windows host within a controlled network (or with TLS + OAuth/api-key + IP allowlist), where an MCP client can safely authenticate and where tool risk tiers (tier1/2 vs tier3) can be constrained.","avoid_when":"Avoid exposing the server broadly to the internet, using no auth, or enabling tier3 tools unless you have strong operational controls and understand the destructive capabilities.","last_evaluated":"2026-03-30T13:51:02.088178+00:00","has_mcp":true,"has_api":false,"auth_methods":["API key bearer token (auth-key)","OAuth 2.0 (embedded authorization server)","IP allowlisting (network-level access control)"],"has_free_tier":false,"known_gotchas":["Tier 3 tools are destructive and are disabled by default; agents must avoid enabling/discovering destructive tools unless explicitly intended.","Remote GUI actions are stateful and may fail due to focus/window/permission/desktop state differences (no explicit guidance on retries/idempotency in the README).","When exposing beyond localhost, ensure TLS and strict IP allowlisting; otherwise agents may connect from unintended networks.","OAuth setup requires client ID/secret and TLS per README guidance; misconfiguration can prevent MCP client authentication."],"error_quality":0.0}