Skip to content

Webskan MCP server

io.github.kamilobstawskiagent-ux/webskankamilobstawskiagent-uxstreamable-httpv0.1.0Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Webskan MCP server can do

The Webskan MCP server is published by the GitHub account kamilobstawskiagent-ux. It has 4 tools. It can create or change data (3 tools: scan_website, audit_website and recheck_website), but cannot delete data. 1 tool only reads.

4 tools bring in text other people can write (scan_website, audit_website, get_audit and 1 more); 2 tools can send data out of your system (scan_website and audit_website).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • 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).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "audit_website" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Starts 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 pages they sit on, per-page SEO (title, description, H1, canonical, alt texts, Open Graph), Lighthouse mobile and desktop, WCAG accessibility (axe) with selectors, HTTPS/TLS/security headers, robots/sitemap, platform detection and customer journeys (menu, search, forms, 404). No LLM, deterministic, read-only. Free plan: 2 audits per IP per 24 h and 1 per host per 24 h (a repeat call for the same host returns the existing audit). With Authorization: Bearer <Webskan Developer license key>: 30 per 24 h.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • 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 Lighthous…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "recheck_website" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Runs 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 with get_audit) and counted against the same limits (free: 2 audits per IP per 24 h).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • 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, …Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Quick 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, Open Graph, mixed content. Takes 30-60 s; waits up to 90 s and otherwise returns status "pending" with a scanId – call again with the same URL in 30 s. Results per host are cached for 24 h (field cached: true). Free, 10 calls per hour per IP. Use it right after a deploy as a smoke check; use audit_website for the whole site.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • 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+deskt…Reads text others writeNo findings

    Why it is in this group

    • The name "get_audit" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns 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 found on; every id is documented at https://webskan.com/developers/findings/), pagesCrawled, finalUrl, platform. For a re-check it also returns diff: fixed / open / new / unverified findings and Lighthouse before/after. Poll every 20-30 s while status is queued or running.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:22 UTC, unchanged since Nov 7, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://webskan.com/mcp: tools/list returned 4 tools to an anonymous client, including scan_website (write), audit_website (write), recheck_website (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "audit_website" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "start": a word for a change.

    What this check looks for
  • The server marks "recheck_website" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__webskan__get_audit"
    ],
    "ask": [
      "mcp__webskan__scan_website",
      "mcp__webskan__audit_website",
      "mcp__webskan__recheck_website"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as webskan. Review it before you use it.

Capability tags behind 4 rules
  • mcp__webskan__scan_website untrusted-input, outbound
  • mcp__webskan__audit_website untrusted-input, outbound
  • mcp__webskan__get_audit untrusted-input
  • mcp__webskan__recheck_website untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kamilobstawskiagent-ux/webskan/verify?hash=da140bddc6293eb2d02a485fb4104952897e59fa5700d237e7fcd6458ce4a237" | jq -e '.changed == false'

Pinned hash da140bddc629, from Nov 21, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.kamilobstawskiagent-ux/webskan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.kamilobstawskiagent-ux/webskan
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.kamilobstawskiagent-ux/webskan.svg)](https://radar.anlyon.com/servers/io.github.kamilobstawskiagent-ux/webskan)

Source: MCP Registry · repository. Synced Nov 7, 2026, 00:17 UTC.

Webskan MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Webskan MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Webskan MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Webskan MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Webskan MCP server have?

4 tools: 3 write, 1 read. scan_website, audit_website, recheck_website and get_audit.

Does the Webskan MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Webskan MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_website and audit_website.

Has the Webskan MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.