io.github.bgaze/snapstack-server

MCPattested
v1.2.3io.github.bgazeUnknownUpdated 2mo agonpmGitHub

Local always-on server for SnapStack: browser capture intake + MCP over 127.0.0.1.

The SnapStack server is a single always-on Node process: it receives browser captures from the extension, stacks them on disk, and serves them to any MCP-capable LLM client over Streamable HTTP. It listens only on — nothing ever leaves your machine. New here? The full install + usage guide lives in the extension README: snapstack-extension. This page is the technical reference. One always-on…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2mo agoLast update
Package
Authorio.github.bgaze
LicenseUnknown
Version1.2.3
Sourcemcp-registry
npmsnapstack-server
GitHubbgaze/snapstack-server
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · efad44b
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv1.2.3 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

The SnapStack server is a single always-on Node process: it receives browser captures from the extension, stacks them on disk, and serves them to any MCP-capable LLM client over Streamable HTTP. It listens only on — nothing ever leaves your machine. New here? The full install + usage guide lives in the extension README: snapstack-extension. This page is the technical reference. One always-on process serves both the extension (capture) and your MCP client, decoupled by a folder on disk. Capture…

Keywords
mcp