Screen Capture MCP (Sherif-Aboulnasr/Agent-Screen-Capture-MCP) is an MCP server listed on the M8ven Trust Index. It scores 68 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Caution

68/100

Screen Capture MCP

Item: Screen Capture MCP
Rating: 68
Author: M8ven

Enables AI agents to capture screen regions by defining a visual overlay or arbitrary coordinates, returning base64 PNG images.

→ Sherif-Aboulnasr/Agent-Screen-Capture-MCP · listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

Sherif-Aboulnasr

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

⚠️

Tool annotations don’t match behaviour

4 read-only tools perform write/delete/exec — capture_viewport (line 126: execFileSync("screencapture", [...screencaptureArgs, "-x", file], { timeout: 10000 })); capture_region (line 126: execFileSync("screencapture", [...screencaptureArgs, "-x", file], { timeout: 10000 })); list_windows (line 234: execFileSync("osascript", ["-l", "JavaScript", "-e", JXA_LIST_WINDOWS], {)

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

// tools this server exposes5 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

capture_viewport

get_viewport_info

Get the current viewport coordinates and overlay status without taking a screenshot.

capture_region

list_windows

capture_window

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configSCREEN_CAPTURE_VIEWPORT_FILE

// quality suggestions

All four hints declared on every tool

5/5 tools missing one or more hints — capture_viewport (missing: destructiveHint, idempotentHint); get_viewport_info (missing: destructiveHint, idempotentHint); capture_region (missing: destructiveHint, idempotentHint), +2 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool annotations match behaviour

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Destructive tools are labelled

3 tools perform destructive updates without destructiveHint — capture_viewport deletes at line 147 (unlinkSync(file)); capture_region deletes at line 147 (unlinkSync(file)); capture_window deletes at line 147 (unlinkSync(file))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/sherif-aboulnasr/agent-screen-capture-mcp?variant=verified)](https://m8ven.ai/mcp/sherif-aboulnasr/agent-screen-capture-mcp)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: cef8929c48821f33dcf8864a0b886653a88c5feb

code hash: d411eddcdc7451d815fa060e4479a537383c854465999d7f495705857809fd2d

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client