Capture Screen MCP
NUGET · CAPTURESCREENMCP
Windows screen capture MCP server with display, region, and active-window capture tools.
Available components
Last scanned (18 hours ago)
Scores higher than 68% of NuGet servers
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 200 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 437 tokens (~62/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_capture_images_by_datetime" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed nuget/CaptureScreenMcp@1.0.5
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | ochtum |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository | https://github.com/ochtum/CaptureScreenMCP |
|---|---|
| Repository type | git |
| Branch | refs/heads/pre_2.0.0 |
| Commit | e0f75e154dd8a7d07642c9ec2926f70dfec751fb |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capture_active_window ~57
Capture the currently active window and save as PNG.
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string|null | – | Full output path like C:\tmp\active_window.png. If omitted, auto-generates under CAPTURE_SCREEN_OUTPUT_DIR or C:\capture_screen. |
No output schema declared.
No examples provided.
capture_display ~100
Capture a specific display (monitor) and save as PNG.
| Name | Type | Req | Description |
|---|---|---|---|
| display | – | – | Monitor selector. Use monitor index (1..n), or primary/left/right/プライマリ/左/右. If omitted, uses CAPTURE_SCREEN_DEFAULT_DISPLAY or primary. |
| outputPath | string|null | – | Full output path like C:\tmp\monitor1.png. If omitted, auto-generates under CAPTURE_SCREEN_OUTPUT_DIR or C:\capture_screen. |
No output schema declared.
No examples provided.
capture_region ~94
Capture a screen region and save as PNG.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Region height (>0). |
| outputPath | string|null | – | Full output path like C:\tmp\region.png. If omitted, auto-generates under CAPTURE_SCREEN_OUTPUT_DIR or C:\capture_screen. |
| width | integer | yes | Region width (>0). |
| x | integer | yes | Left coordinate. |
| y | integer | yes | Top coordinate. |
No output schema declared.
No examples provided.
capture_screen ~54
Capture full virtual desktop and save as PNG.
| Name | Type | Req | Description |
|---|---|---|---|
| outputPath | string|null | – | Full output path like C:\tmp\shot.png. If omitted, auto-generates under CAPTURE_SCREEN_OUTPUT_DIR or C:\capture_screen. |
No output schema declared.
No examples provided.
delete_all_capture_images ~22
Delete all capture image files in CAPTURE_SCREEN_OUTPUT_DIR.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_capture_images_by_datetime ~91
Delete capture images by date or datetime range using file modified time.
| Name | Type | Req | Description |
|---|---|---|---|
| endDatetime | string|null | – | Upper bound in YYYY-MM-DD HH:MM[:SS] (inclusive). |
| startDatetime | string|null | – | Lower bound in YYYY-MM-DD HH:MM[:SS] (inclusive). |
| targetDate | string|null | – | Date in YYYY-MM-DD. Deletes files modified on that day. |
No output schema declared.
No examples provided.
list_displays ~19
List all connected displays with bounds and primary flag.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Capture Screen MCP server?
Capture Screen MCP runs locally as a NuGet package, launched with dnx CaptureScreenMcp@1.0.5 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · CaptureScreenMcp
claude mcp add ochtum-capture-screen -- dnx CaptureScreenMcp@1.0.5 --yes
What is the Capture Screen MCP server?
Capture Screen MCP is listed in the public MCP registry as io.github.ochtum/capture-screen. Windows screen capture MCP server with display, region, and active-window capture tools. This page covers its NuGet package (CaptureScreenMcp).
Is the Capture Screen MCP server safe to use?
Capture Screen MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Capture Screen MCP server expose?
Capture Screen MCP exposes 7 tools: capture_screen, list_displays, capture_active_window, capture_display, delete_capture_images_by_datetime, and 2 more. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Is the Capture Screen MCP server still maintained?
Capture Screen MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.