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.siteglass/mcp

NPM · SITEGLASS-MCP

Archive any URL to a shareable rrweb/pdf/png snapshot + agent-driven web QA (scan, run E2E flows).

Available components

0 this week 80 Trust /100

Last scanned (7 hours ago)

Scores higher than 65% of npm servers

Category Testing and QA

Trust breakdown (7 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 → 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
  • 30 of 92 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 117 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 636 tokens (~57/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
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; "siteglass_feedback" implies "send" 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 11 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
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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.90 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 22 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
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 5 Nov 2026 · Analysed npm/siteglass-mcp@0.1.5

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~636 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. 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 →

Tool Tokens
siteglass_feedback ~45

Send feedback to the siteglass team (bugs, missing features, anything). Works for agents and people alike.

NameTypeReqDescription
contextstring––
messagestringyes–

No output schema declared.

No examples provided.

siteglass_generate_flows ~42

Derive executable E2E test flows from a scan (LLM). Step 4. Returns flow ids.

NameTypeReqDescription
crawl_idstringyes–

No output schema declared.

No examples provided.

siteglass_get_render ~39

Fetch an archive once its Lightning invoice is paid. Returns the permalink when ready, or a pending status.

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

siteglass_get_run ~43

Read a flow run's per-step results + capture URLs by run_id (use after siteglass_run_flow if still running).

NameTypeReqDescription
run_idstringyes–

No output schema declared.

No examples provided.

siteglass_get_scan ~40

Read a scan's report + findings by crawl_id (use after siteglass_scan if it was still running).

NameTypeReqDescription
crawl_idstringyes–

No output schema declared.

No examples provided.

siteglass_register_site ~59

Register a web app (its deployed URL) with siteglass and get an ownership-proof token to place on it. Step 1.

NameTypeReqDescription
urlstringyesThe app's URL, e.g. https://myapp.lovable.app

No output schema declared.

No examples provided.

siteglass_render ~170

Archive ANY public web page for a few sats — a permanent, shareable snapshot, returned as a permalink. The bot-friendly alternative to archive.today: no CAPTCHA, no signup, no ownership verification, callable programmatically. Default 'rrweb' captures the live rendered DOM (navigable, post-JS, selectable text + working links); 'pdf' is a single continuous page; 'png' a full-page image. Anonymous calls return a Lightning invoice (pay, then call siteglass_get_render); if your account has credits it archives immediately and returns the permalink.

NameTypeReqDescription
formatstring–rrweb (default, interactive DOM archive), pdf (single continuous page), or png (full-page image)
urlstringyesAny public URL, e.g. https://example.com

No output schema declared.

No examples provided.

siteglass_run_flow ~60

Run one test flow. Returns a run_id; if still running, poll with siteglass_get_run. Step 5.

NameTypeReqDescription
flow_idstringyes–
fullboolean–true = submit destructive actions for real (default false)

No output schema declared.

No examples provided.

siteglass_scan ~49

Crawl a verified site (first scan per site is free). Returns a crawl_id; if still running, poll with siteglass_get_scan. Step 3.

NameTypeReqDescription
site_idstringyes–

No output schema declared.

No examples provided.

siteglass_set_credentials ~50

Provide a test account (username/password) so authenticated flows can log in to the site.

NameTypeReqDescription
passwordstringyes–
site_idstringyes–
usernamestringyes–

No output schema declared.

No examples provided.

siteglass_verify_site ~39

Check that the ownership-proof token is live on the site. Step 2 (after placing the token).

NameTypeReqDescription
site_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.siteglass/mcp server?

io.siteglass/mcp runs locally as an npm package, launched with npx -y siteglass-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 · siteglass-mcp

# add to Claude Code
claude mcp add io-siteglass-mcp -- npx -y siteglass-mcp
Common questions

What is the io.siteglass/mcp server?

io.siteglass/mcp is listed in the public MCP registry as io.siteglass/mcp. Archive any URL to a shareable rrweb/pdf/png snapshot + agent-driven web QA (scan, run E2E flows). This page covers its npm package (siteglass-mcp).

Is the io.siteglass/mcp server safe to use?

io.siteglass/mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.siteglass/mcp server expose?

io.siteglass/mcp exposes 11 tools: siteglass_register_site, siteglass_verify_site, siteglass_scan, siteglass_get_scan, siteglass_generate_flows, and 6 more. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.

Is the io.siteglass/mcp server still maintained?

io.siteglass/mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.siteglass/mcp server under?

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