io.github.bgaze/snapstack-server
NPM · SNAPSTACK-SERVER · SCANNED SEP 20
Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1.
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bgaze/snapstack-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 103 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 273 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 (33% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_screenshots" 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 3 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.bgaze/snapstack-server MCP server?
io.github.bgaze/snapstack-server runs locally as an npm package, launched with npx -y snapstack-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · snapstack-server
claude mcp add bgaze-snapstack-server -- npx -y snapstack-server
{
"mcpServers": {
"bgaze-snapstack-server": {
"command": "npx",
"args": [
"-y",
"snapstack-server"
]
}
}
} {
"servers": {
"bgaze-snapstack-server": {
"command": "npx",
"args": [
"-y",
"snapstack-server"
]
}
}
} codex mcp add bgaze-snapstack-server -- npx -y snapstack-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bgaze-snapstack-server": {
"type": "local",
"command": [
"npx",
"-y",
"snapstack-server"
],
"enabled": true
}
}
} openclaw mcp add bgaze-snapstack-server --command npx --arg -y --arg snapstack-server
mcp_servers:
bgaze-snapstack-server:
command: "npx"
args: ["-y", "snapstack-server"] {
"McpServers": {
"bgaze-snapstack-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"snapstack-server"
]
}
}
} assistant mcp add bgaze-snapstack-server -t stdio -c npx -a -y snapstack-server
{
"mcpServers": {
"bgaze-snapstack-server": {
"command": "npx",
"args": [
"-y",
"snapstack-server"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.83 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 20 Sept 2026 · Analysed npm/snapstack-server@1.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bgaze/snapstack-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bgaze/snapstack-server/.github/workflows/publish.yml@refs/tags/v1.2.3 |
| Rekor log index | 1764741687 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:aa6067d73c9387018666dcc12a93d59ad92cbf09b98e85ef7a043e709dc765bdad8f37d4780ab3453e34a4b7b082f84912a2f0d1f329014a3395e651c |
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 →
clear_screenshots Clear screenshots ~84
Delete pending screenshots from the stack. Pass "numbers" to delete only specific captures (e.g. [1] or [2,3]); omit to clear the whole stack. Once the stack is empty, numbering restarts at 01.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | – | Capture numbers to delete (e.g. [2,3]). Omit to clear all. |
No output schema declared.
No examples provided.
count_screenshots Count screenshots ~25
Return the number of pending screenshots in the stack without retrieving or clearing them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_screenshots Get screenshots ~164
List the pending browser screenshots as a manifest — NO image data. The stack is the local folder where the SnapStack browser extension pushes captures. Each entry has a stable two-digit "number", the absolute local "path", "width"/"height", and metadata (url, title, capturedAt, format, bytes). Read the file at "path" yourself only if you need the pixels. This tool does NOT delete anything — use clear_screenshots to remove captures. Pass "numbers" to list only specific captures (e.g. [1] or [1,3]); omit to list them all.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | – | Capture numbers to include (e.g. [1] or [1,3,5]). Omit to include all. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| missing | array | yes | – |
| screenshots | array | yes | – |
No examples provided.
What is the io.github.bgaze/snapstack-server MCP server?
io.github.bgaze/snapstack-server is an MCP server listed in the public MCP registry as io.github.bgaze/snapstack-server. Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1. This page covers its npm package (snapstack-server).
Is the io.github.bgaze/snapstack-server MCP server safe to use?
io.github.bgaze/snapstack-server scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.bgaze/snapstack-server MCP server expose?
io.github.bgaze/snapstack-server exposes 3 tools: get_screenshots, clear_screenshots, count_screenshots. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Is the io.github.bgaze/snapstack-server MCP server still maintained?
io.github.bgaze/snapstack-server is still listed as active in the MCP registry. We last reached this channel on 20 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.bgaze/snapstack-server MCP server under?
io.github.bgaze/snapstack-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.