Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.bickov/slimsnap

NPM · @SLIMSNAP/MCP · SCANNED AUG 3

Your recent screen captures as structured JSON your AI agent can read. Local only, no network.

Available components

65 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @slimsnap/mcp

# add to Claude Code
claude mcp add bickov-slimsnap -- npx -y @slimsnap/mcp
# add to Codex CLI
codex mcp add bickov-slimsnap -- npx -y @slimsnap/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bickov-slimsnap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@slimsnap/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add bickov-slimsnap --command npx --arg -y --arg @slimsnap/mcp
# ~/.hermes/config.yaml
mcp_servers:
  bickov-slimsnap:
    command: "npx"
    args: ["-y", "@slimsnap/mcp"]
// mcp.json
{
  "mcpServers": {
    "bickov-slimsnap": {
      "command": "npx",
      "args": [
        "-y",
        "@slimsnap/mcp"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +44
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 28

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@slimsnap/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 4 exposed · ~350 tokens

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.

Tool Tokens
get_capture ~45

Returns one specific capture as structured JSON, same shape as get_latest_capture. Get ids from list_captures.

NameTypeReqDescription
idstringyesCapture id from list_captures.

No output schema declared.

No examples provided.

get_capture_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.

NameTypeReqDescription
frameinteger1-based frame number. Scroll captures have several, top to bottom.
idstringCapture id. Omit to use the newest capture.

No output schema declared.

No examples provided.

get_latest_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 ~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.

NameTypeReqDescription
limitintegerHow many captures to return. Default 10.
NameTypeReqDescription
capturesarrayyes
countintegeryes

No examples provided.