Webskan

io.github.kamilobstawskiagent-ux/webskan · v0.1.0 · security

Webskan is healthy: it completed an MCP handshake in 478 ms and exposes 4 tools.

Audit and re-check a live website: Lighthouse, SEO, accessibility, security, links, journeys.

Endpoint: https://webskan.com/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency478 ms
Last checked (UTC)2026-11-07T03:30:48.821Z

Health history

Checked (UTC)StatusLatencyError
2026-11-07T03:30:48.821ZHealthy478

Tools (4)

scan_websiteQuick scan of one page (the URL you pass, usually the home page): Lighthouse mobile scores (performance, accessibility, best practices, SEO) with LCP/CLS/TBT/page weight/requests, plus HTTPS redirect, TLS, HSTS and security headers, title, meta description, H1, image alt texts, viewport, canonical,
audit_websiteStarts a full technical audit of a whole website and returns immediately with an auditId (poll get_audit every 20-30 s; typically done in 1-5 min). The audit crawls up to `pages` pages (1-30, default 15) following internal links and the sitemap, and checks: broken internal/external links with the pa
get_auditReturns the status (queued / running with ETA) or the finished result of an audit started with audit_website or recheck_website: summary counts by severity, Lighthouse mobile+desktop scores, findings sorted high → medium → low → info (each with id, area, severity, title, detail and the pages it was
recheck_websiteRuns the same audit again (same URL, same number of pages) linked to the original auditId, so get_audit returns a diff: fixed / still open / new / unverified findings and Lighthouse before → after. Call it after you have deployed fixes. Asynchronous like audit_website (returns a new auditId to poll