SnapSweep

npx add-mcp 'https://mcp.snapsweep.dev/mcp'

A real-browser smoke test your AI agent can run on your site.

SnapSweep is an MCP server for coding agents. Point it at a public site you own and it loads up to 10 pages in a real browser, follows the links, checks the elements you name, and records console and network errors, with screenshots as evidence. It calls something broken only after reproducing the failure. It never clicks, submits forms or logs in.

Install in one line · Claude Code

claude mcp add --transport http --scope user snapsweep https://mcp.snapsweep.dev/mcp --header "Authorization: Bearer YOUR_SNAPSWEEP_KEY"

Good fit today

• Public marketing sites, docs, landing pages and the public pages of an app.
• A host where you can add one DNS TXT record (ownership proof, per exact host).
• A quick check after a deploy, or on a schedule with the report emailed to you.

Not yet

• localhost or private networks: the hosted service refuses them.
• Pages behind a login, and flows that need clicks or form submits.
• More than 10 pages in one scan.

Start in three steps

1. Get a key. One API call with your email, then confirm from the email. The key is shown once, and verifying adds 1,000 free credits. Quickstart
2. Connect your agent. Add https://mcp.snapsweep.dev/mcp with an Authorization: Bearer header holding your key. Claude Code is verified; Cursor and other clients are not yet.
3. Prove the host, then scan. SnapSweep scans only hosts you control: your agent calls snapsweep_verify_domain, you publish one DNS TXT record, and it can start scanning. How the proof works

Finds what breaks for visitors

Broken links and navigation, missing elements, console errors and failed network requests, checked in a real browser on up to 10 pages per scan, plus an advisory Lighthouse pass on the start page, an edge audit of security headers and TLS certificate expiry, and a visual regression check that compares each page with the previous scan of the same target.

Broken means reproduced

SnapSweep reports broken only after an assertion failed and its paired control check held. Anything it could not prove stays unconfirmed, never a guess. It does not yet certify anything as working: judge each check by its outcome, passed or failed.

Built to be read-only

It loads pages with plain GET requests, focuses and hovers. It never clicks, submits forms or logs in, skips links whose path or query looks like logout, delete, unsubscribe or cancel, and follows your robots.txt. Scans only run on hosts you have proved you own. A data-changing link it does not recognize could still be hit, so exclude sensitive paths in robots.txt.

Results sized for an agent

Results come back paged, 50 findings at a time (100 at most) with a cursor. Ask for view: "summary" first: one small object with the verdict, exact counts and every defect. Then fetch only the findings you need.

Also: scheduled scans with each report emailed to you (monitoring), and optional auto-reload of credits, which is off by default: you opt in to turn it on, and cancel any time (pricing).

What we can show you

• We run it on this site. A daily scan of snapsweep.dev uses the same public service customers use, and the raw report is published, failures included. 56 passed, 0 failed, 6 inconclusive behaviour checks across 10 of 10 pages tested. As of 2026-10-09 09:11 UTC. Read the full report.
• Prices from measurements. 20 scans of one production Next.js site we operate, September 2026. Raw numbers are in pricing.json.
• Named data processors. To help explain a finding, redacted page text (never screenshots) can go to api.deepseek.com and openrouter.ai. Privacy policy
• A polite crawler. It identifies itself as SnapSweepBot/0.1 and follows robots.txt. About the crawler
• Who we are. SnapSweep is a product of Loomworks Solutions LLC. To reach us, write to hello@snapsweep.dev.

What a scan costs

A 10-page scan cost about 210 credits ($0.21) with the hosted defaults (Lighthouse on) in our tests, and your site will differ. To start, a scan needs 340 credits free for 10 pages; they are held, released in full when the scan ends, and you pay for the work done. With max_credits set, a capped scan bills at most the lower of max_credits and its high estimate. Without it, the only limit is your balance, which the last step can take slightly negative. These figures are refined as more sites are measured. How billing works

Start here: docs · get a key · FAQ