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

io.github.reeinharddd/snapmcp

NPM · SNAPMCP · SCANNED AUG 23

Visual capture MCP server: terminal colors, code, diffs, PDFs, GIFs. 13 tools, SSRF on by default.

Available components

37 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 Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • 48 of 148 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.reeinharddd/snapmcp MCP server?

io.github.reeinharddd/snapmcp runs locally as an npm package, launched with npx -y snapmcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · snapmcp

# add to Claude Code
claude mcp add reeinharddd-snapmcp -- npx -y snapmcp
// .cursor/mcp.json
{
  "mcpServers": {
    "reeinharddd-snapmcp": {
      "command": "npx",
      "args": [
        "-y",
        "snapmcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "reeinharddd-snapmcp": {
      "command": "npx",
      "args": [
        "-y",
        "snapmcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add reeinharddd-snapmcp -- npx -y snapmcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "reeinharddd-snapmcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "snapmcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add reeinharddd-snapmcp --command npx --arg -y --arg snapmcp
# ~/.hermes/config.yaml
mcp_servers:
  reeinharddd-snapmcp:
    command: "npx"
    args: ["-y", "snapmcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "reeinharddd-snapmcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "snapmcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add reeinharddd-snapmcp -t stdio -c npx -a -y snapmcp
// mcp.json
{
  "mcpServers": {
    "reeinharddd-snapmcp": {
      "command": "npx",
      "args": [
        "-y",
        "snapmcp"
      ]
    }
  }
}
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.

  • 21 Aug 26 +15
    • Malware scan: unverified → pass security
  • 20 Aug 26 22

    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 23 Aug 2026 · Analysed npm/snapmcp@2.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Install scripts 1 script
Hook Tier Command
postinstall unreviewed bun run scripts/postinstall.ts
Dependencies 148 packages
Packages resolved 148
Stale 48
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.reeinharddd/snapmcp MCP server?

io.github.reeinharddd/snapmcp is an MCP server listed in the public MCP registry as io.github.reeinharddd/snapmcp. Visual capture MCP server: terminal colors, code, diffs, PDFs, GIFs. 13 tools, SSRF on by default. This page covers its npm package (snapmcp).

Is the io.github.reeinharddd/snapmcp MCP server safe to use?

io.github.reeinharddd/snapmcp scores 37 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 2026. 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.

Is the io.github.reeinharddd/snapmcp MCP server still maintained?

io.github.reeinharddd/snapmcp is still listed as active in the MCP registry. We last reached this channel on 23 August 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.reeinharddd/snapmcp MCP server under?

io.github.reeinharddd/snapmcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.