io.github.bickov/slimsnap
NPM · @SLIMSNAP/MCP · SCANNED SEP 22
Your recent screen captures as structured JSON your AI agent can read. Local only, no network.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 350 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (25% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.bickov/slimsnap MCP server?
io.github.bickov/slimsnap runs locally as an npm package, launched with npx -y @slimsnap/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @slimsnap/mcp
claude mcp add bickov-slimsnap -- npx -y @slimsnap/mcp
{
"mcpServers": {
"bickov-slimsnap": {
"command": "npx",
"args": [
"-y",
"@slimsnap/mcp"
]
}
}
} {
"servers": {
"bickov-slimsnap": {
"command": "npx",
"args": [
"-y",
"@slimsnap/mcp"
]
}
}
} codex mcp add bickov-slimsnap -- npx -y @slimsnap/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bickov-slimsnap": {
"type": "local",
"command": [
"npx",
"-y",
"@slimsnap/mcp"
],
"enabled": true
}
}
} openclaw mcp add bickov-slimsnap --command npx --arg -y --arg @slimsnap/mcp
mcp_servers:
bickov-slimsnap:
command: "npx"
args: ["-y", "@slimsnap/mcp"] {
"McpServers": {
"bickov-slimsnap": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@slimsnap/mcp"
]
}
}
} assistant mcp add bickov-slimsnap -t stdio -c npx -a -y @slimsnap/mcp
{
"mcpServers": {
"bickov-slimsnap": {
"command": "npx",
"args": [
"-y",
"@slimsnap/mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +5
- Source repository: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 18 Sept 26 −4
- Provenance: pass → unverified ▼ security
- 16 Sept 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
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 22 Sept 2026 · Analysed npm/@slimsnap/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_capture Get one SlimSnap capture by id ~45
Returns one specific capture as structured JSON, same shape as get_latest_capture. Get ids from list_captures.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Capture id from list_captures. |
No output schema declared.
No examples provided.
get_capture_image Get one frame of a capture as an image ~109
Returns the actual pixels of one frame, already downscaled to a size the model can read. Useful for visual questions that the text and coordinates cannot settle, such as spacing, visual style, colour balance, or imagery with no text in it. Costs substantially more tokens than the structured form of the same capture.
| Name | Type | Req | Description |
|---|---|---|---|
| frame | integer | – | 1-based frame number. Scroll captures have several, top to bottom. |
| id | string | – | Capture id. Omit to use the newest capture. |
No output schema declared.
No examples provided.
get_latest_capture Get the user's most recent SlimSnap capture ~114
Returns the newest SlimSnap capture as structured JSON: every OCR'd text element with its normalised bounding box and colour, plus any annotations the user drew (arrows, boxes, highlights, callouts) and which element each one points at. Use this whenever the user refers to their screen, their last screenshot, 'this', 'here', or something they just marked. Returns no image. The text and coordinates answer most questions about a capture on their own; the pixels are available separately when a question is genuinely visual.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_captures List recent SlimSnap captures ~82
Lists the user's recent captures newest first, with a short text preview of each. This is the cheap summary view; get_capture returns a single capture in full. Useful for finding an earlier capture when the user does not mean the newest one, or for working through several marked screens.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many captures to return. Default 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| captures | array | yes | – |
| count | integer | yes | – |
No examples provided.
What is the io.github.bickov/slimsnap MCP server?
io.github.bickov/slimsnap is an MCP server listed in the public MCP registry as io.github.bickov/slimsnap. Your recent screen captures as structured JSON your AI agent can read. Local only, no network. This page covers its npm package (@slimsnap/mcp).
Is the io.github.bickov/slimsnap MCP server safe to use?
io.github.bickov/slimsnap scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 io.github.bickov/slimsnap MCP server expose?
io.github.bickov/slimsnap exposes 4 tools: get_latest_capture, list_captures, get_capture, get_capture_image. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Is the io.github.bickov/slimsnap MCP server still maintained?
io.github.bickov/slimsnap is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bickov/slimsnap MCP server under?
io.github.bickov/slimsnap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.