{"id":"amafjarkasi-windows-screenshot-mcp-server","name":"windows-screenshot-mcp-server","af_score":39.8,"security_score":19.2,"reliability_score":18.8,"what_it_does":"A Go-based Windows screenshot server that captures window/desktop regions (by title/class/pid/handle) and provides both REST endpoints and MCP (JSON-RPC 2.0) methods for screenshot and window/chrome discovery/capture. It also offers real-time WebSocket streaming and Chrome DevTools-based tab capture (requires launching Chrome with remote debugging).","best_when":"You control the host environment (Windows machine), Chrome launching parameters, and network access to the server, and you want simple local automation/agent integration via REST, WebSocket, and MCP.","avoid_when":"You need robust security boundaries for remote/public access, or you cannot guarantee safe handling of screenshots/streaming over the network and OS-level privacy constraints.","last_evaluated":"2026-04-04T21:20:40.310906+00:00","has_mcp":true,"has_api":true,"auth_methods":["None specified (no authentication mentioned in provided README for REST/WS/MCP)"],"has_free_tier":false,"known_gotchas":["WebSocket streaming endpoints are described but not documented with an explicit reconnection/backoff strategy.","Chrome tab capture requires Chrome to be started with --remote-debugging-port and (optionally) a temp profile; agent workflows must ensure this is set up.","No auth is documented; agents should assume endpoints may be reachable only on trusted networks/environments.","Streaming sessions and max sessions are mentioned (StreamMaxSessions default 10), but session lifecycle limits/error behaviors are not documented in detail."],"error_quality":0.0}