mcpField
W
Webskan

Webskan

Remote
webskan.comDeveloper Tools0Updated 2d ago

About Webskan

Webskan is a remote MCP server and Claude Code plugin for auditing public websites in a real mobile browser. It checks performance, SEO, accessibility, security, links and user journeys, then compares findings after fixes.

Key features

  1. 01Mobile and desktop Lighthouse checks
  2. 02SEO crawl of up to 30 pages
  3. 03WCAG 2.1 AA accessibility checks
  4. 04Security headers and TLS checks
  5. 05Broken links, forms and journeys
  6. 06Finding IDs for exact re-checks

Use cases

  1. 01Audit a site after deployment
  2. 02Find accessibility and SEO issues
  3. 03Re-check findings after fixes
  4. 04Review forms and key user journeys

MCP support

Webskan exposes the `scan_website`, `audit_website`, `get_audit` and `recheck_website` tools through a remote MCP server at `https://webskan.com/mcp`.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://webskan.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://webskan.com/mcpAuth required

Tools

Details

From the project README

Webskan plugin for Claude Code

Audit and re-check the website your agent just shipped. The plugin adds the Webskan remote MCP server (https://webskan.com/mcp) and a /webskan:site-check skill that teaches Claude Code the loop: audit, fix the high and medium findings by id, deploy, re-check, report fixed / still open / new.

What Webskan checks, from the outside, in a real mobile browser: Lighthouse (mobile and desktop), a crawl of up to 30 pages with SEO checks on each, axe-core accessibility (WCAG 2.1 AA), security headers and TLS, broken links, forms, the cookie banner, and customer journeys (404 page, menu, search, cart to checkout). Every finding has a stable id, so the re-check is an exact diff.

Install

In Claude Code:

/plugin marketplace add kamilobstawskiagent-ux/webskan-claude-plugin
/plugin install webskan@webskan

Or from the shell:

claude plugin marketplace add kamilobstawskiagent-ux/webskan-claude-plugin
claude plugin install webskan@webskan

No account and no key are needed for the free plan. If you only want the MCP server without the skill:

claude mcp add --transport http webskan https://webskan.com/mcp

Use

/webskan:site-check https://mysite.com

or just ask: "audit https://mysite.com and fix the high-severity findings, then recheck".

Tools provided by the server: scan_website, audit_website, get_audit, recheck_website. Details, limits of the free plan and configuration for Cursor, VS Code, Codex CLI and other clients: https://webskan.com/developers/

Free plan limits

  • scan_website: 10 per hour per IP (120 per hour overall); results cached 24 h per host, kept 7 days.
  • audit_website / recheck_website: 2 per IP per 24 h and 1 per host per 24 h; 1-30 pages; results kept 30 days.
  • Public websites only - no localhost, private networks or sites behind a login.

Developer plan ($29/month): 30 whole-site audits per 24 h per key and no one-audit-per-host-per-day window. Pass the key as Authorization: Bearer <key> (an http server with headers in your MCP config). Details: https://webskan.com/developers/#teams

Layout

.claude-plugin/marketplace.json      marketplace "webskan"
plugins/webskan/
  .claude-plugin/plugin.json         plugin manifest
  .mcp.json                          remote MCP server
  skills/site-check/SKILL.md         the audit -> fix -> recheck loop

License

MIT. Contact: [email protected]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.