ScreenCue
Lightweight native desktop hints for AI agents. Rust, MCP, Windows, macOS and Linux X11.
No outside reports on file
ScreenCue is distributed via GitHub (CrioNIK/ScreenCue); review its source code, dependencies, and requested permissions before use.
Based on public adoption and transparency signals as of Oct 24, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourceGitHub (CrioNIK/ScreenCue)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
No npm or PyPI package is listed. Install from source: github.com/CrioNIK/ScreenCue ↗
About ScreenCue
ScreenCue is an MCP server focused on General: Lightweight native desktop hints for AI agents. Rust, MCP, Windows, macOS and Linux X11.
It is hosted on GitHub at CrioNIK/ScreenCue (2 GitHub stars). Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
No npm or PyPI package is listed for this MCP server. Source code and setup steps: github.com/CrioNIK/ScreenCue.
Why this grade
Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 2
- Listing last refreshed
- 2026-10-25
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
No reports found for this package in our research (last checked 2026-10-29).
Risks to watch for
- Dependency & version pinning: Distributed via GitHub (CrioNIK/ScreenCue). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install ScreenCue?
ScreenCue does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/CrioNIK/ScreenCue.
Are there security reports about ScreenCue?
No reports found for this package in our research (last checked 2026-10-29). ScreenCue currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is ScreenCue actively maintained?
ScreenCue has 2 GitHub stars. Our directory data was last refreshed on 2026-10-25. Check recent commit activity, release tags, and open issues at github.com/CrioNIK/ScreenCue before pinning it in production.
What are alternatives to ScreenCue?
Compare ScreenCue side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.
README badge and team notes
Maintain or use ScreenCue? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/crionik-screencue)HTML embed:
<a href="https://agentarmorhq.com/skills/crionik-screencue"><img src="https://agentarmorhq.com/api/badge/crionik-screencue" alt="AgentArmorHQ Risk Grade for ScreenCue" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "crionik-screencue"Share with your security lead
Need sign-off to use ScreenCue? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: ScreenCue
- **Listing URL:** https://agentarmorhq.com/skills/crionik-screencue
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 2 GitHub stars
#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** GitHub (CrioNIK/ScreenCue)
#### Recommended Hardened Setup
- **Source Repo:** https://github.com/CrioNIK/ScreenCue
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 24, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- App connector
- Publisher
- CrioNIK
- Source code
- github.com/CrioNIK/ScreenCue
- Est. context load
- ~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
- Popularity
- 2 GitHub stars
- Last updated
- 2026-10-25
- Last graded
- 2026-10-25
Community
Discussions for ScreenCue
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude