siteglass-mcp (siteglassio/siteglass-mcp) is an MCP server listed on the M8ven Trust Index. It scores 64 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

C
Caution
64/100

siteglass-mcp

Enables archival of any public URL as interactive snapshot (rrweb, PDF, PNG) and autonomous web QA for apps (register, scan, generate and run end-to-end flows).

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

siteglassio

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SITEGLASS_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
4 tools describe read intent but their handlers mutate — siteglass_register_site (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true })); siteglass_verify_site (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true })); siteglass_get_scan (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true }))
🔐
You'll be asked for 1 credential: SITEGLASS_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes12 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

siteglass_register_site

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

siteglass_verify_site

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

siteglass_scan

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

siteglass_get_scan

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

siteglass_generate_flows

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

siteglass_run_flow

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

siteglass_get_run

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

siteglass_render

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, selec

siteglass_get_render

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

siteglass_set_credentials

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

siteglass_feedback

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

siteglass_scan_local

Scan a web app you're building — FREE: no account, no ownership verification, no payment. Runs a headless browser on YOUR machine to crawl the URL (works on http://localhost:PORT or any URL your machine can reach — nothing is tunneled to siteglass), then siteglass analyzes the crawl server-side and

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSITEGLASS_API_KEYto use your own); the first scan per site is free, then scans
configSITEGLASS_BASE_URL
// quality suggestions

Dependencies

2 runtime dependencies, 1 flagged: playwright

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — siteglass_register_site (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); siteglass_verify_site (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); siteglass_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

4 tools describe read intent but their handlers mutate — siteglass_register_site (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true })); siteglass_verify_site (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true })); siteglass_get_scan (line 41: fs.mkdirSync(path.dirname(KEY_FILE), { recursive: true }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Tool description accuracy

4 tools have description/behavior mismatches: siteglass_register_site: description implies read-only but handler writes/deletes/executes; siteglass_verify_site: description implies read-only but handler writes/deletes/executes; siteglass_get_scan: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/siteglassio/siteglass-mcp?variant=verified)](https://m8ven.ai/mcp/siteglassio/siteglass-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 881c376af21c18a70a02471b43071bcd5d1c2761
code hash: c0934d3610a18dedbc8e0b6fe58c8ef65156f774b727ee618c26dc22cc40404a
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client