Skip to content

Web Scan MCP server

io.github.ankitkumarjha515/web-scanankitkumarjha515streamable-httpv1.0.0Scanned

Audit any live URL: 85 SEO, AI-search, security, leaked-key and speed checks, with fixes to verify.

3 tools: 2 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Web Scan MCP server can do

The Web Scan MCP server is published by the GitHub account ankitkumarjha515. It has 3 tools. It can create or change data (2 tools: scan_url and verify_fixes), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (scan_url, verify_fixes and get_report); 2 tools can send data out of your system (scan_url and verify_fixes).

The fixed checks matched 1 finding (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 16, 2026, version 1.0.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.

3 tools

Changes things 2Claude Code: ask
  • scan_urlRun a fresh Web Scan audit of a public URL and return its score (0-100), grade, and every failing or warning check with its id, title and fix: the result is complete in itself.Reads text others writeCan send data out1 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.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "scan_url" 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
    Run a fresh Web Scan audit of a public URL and return its score (0-100), grade, and every failing or warning check with its id, title and fix: the result is complete in itself. reportUrl is a shareable link only when the request carries a signed-in Web Scan token (reports are saved for signed-in users only); otherwise it is null and nothing is stored. fullReportUrl is always present: the full report on the website, to share with the user. Use this first, to find out what to fix on a live page. Takes about 5-15 seconds. Cannot scan localhost or private networks; use a deployed or preview URL.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • verify_fixesRe-scan a URL after you deployed fixes and report, per check id, whether it now passes (fixed: true), plus the new score, the previous score, what is still failing with its fix, an…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
    Re-scan a URL after you deployed fixes and report, per check id, whether it now passes (fixed: true), plus the new score, the previous score, what is still failing with its fix, and allFixed. Use this after a change reaches production (or a public preview) instead of asking the user to re-scan. Pass the check ids from the scan or fix prompt; with none, every failing or warning check is returned. If a fix you made still shows fixed: false, the deploy may not be live yet or a CDN may be serving a cached page: wait about a minute and call again before concluding the fix failed.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_reportRead a stored Web Scan report by its slug (the part after /r/ in an agentmarket.lol/web-scan/r/<slug> link) without re-scanning: score, grade, scan time and the failing or warning …Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read a stored Web Scan report by its slug (the part after /r/ in an agentmarket.lol/web-scan/r/<slug> link) without re-scanning: score, grade, scan time and the failing or warning checks with fixes. Use this when the user shares a report link. Reports expire after two weeks; to check the current state of a site, use scan_url or verify_fixes instead.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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 write3
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 20, 2026, 19:02 UTC, unchanged since Oct 22, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://preflight-api.agentmarket.lol/api/mcp: tools/list returned 3 tools to an anonymous client, including scan_url (write), verify_fixes (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "scan_url" 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 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http web-scan https://preflight-api.agentmarket.lol/api/mcp
claude mcp add --transport http web-scan https://preflight-api.agentmarket.lol/api/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__web-scan__get_report"
    ],
    "ask": [
      "mcp__web-scan__scan_url",
      "mcp__web-scan__verify_fixes"
    ],
    "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 web-scan. Review it before you use it.

Capability tags behind 3 rules
  • mcp__web-scan__scan_url untrusted-input, outbound
  • mcp__web-scan__verify_fixes untrusted-input, outbound
  • mcp__web-scan__get_report 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.ankitkumarjha515/web-scan/verify?hash=4058f95cfee079cb5a10246bc109bd2124d51c268c97f16e79717d35df025eac" | jq -e '.changed == false'

Pinned hash 4058f95cfee0, from Nov 16, 2026, 09: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.ankitkumarjha515/web-scan/changes.xml

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

Badge

Anlyon Radar badge for io.github.ankitkumarjha515/web-scan
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ankitkumarjha515/web-scan.svg)](https://radar.anlyon.com/servers/io.github.ankitkumarjha515/web-scan)

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:22 UTC.

Web Scan MCP server: questions and answers

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

Is the Web Scan MCP server safe?

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

Can the Web Scan MCP server delete data?

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

Can the Web Scan 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 Web Scan MCP server have?

3 tools: 2 write, 1 read. scan_url, verify_fixes and get_report.

Does the Web Scan MCP server need sign-in or OAuth?

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

Does the Web Scan 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_url and verify_fixes.

Has the Web Scan MCP server changed its tools?

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