Screen Control MCP server
Safety-gated computer use for AI agents: screen OCR and vision, mouse, keyboard, window control.
B70/100grade B
Adoption
New
1 stars
Reviews
Write oneNobody has reviewed Screen Control yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Screen Control tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
Screen Control: common questions
- Is Screen Control MCP server safe?
- Mostly: it is graded B (70/100). Read the Screen Control safety report
- Does Screen Control need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Screen Control maintained?
- The last commit was 3 days ago (2026-09-17). The latest release is v1.0.0.
- What can I use instead of Screen Control?
- Servers from other publishers that do the same job: SSH — policy-gated remote access MCP server.
Alternatives to Screen Control
Same job from other publishers: the closest match first, then the best rated.
- SSH — policy-gated remote accessPolicy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.not reviewedEstablishedB
