Webscan MCP Server

MCP server for web content scanning and analysis

Local serverstdio

What is the Webscan MCP server?

Webscan MCP server exists for a simple reason — assistants are far more useful when they can act on Webscan directly instead of describing what you should do. MCP server for web content scanning and analysis.

What you get

A Model Context Protocol (MCP) server for web content scanning and analysis. This server provides tools for fetching, analyzing, and extracting information from web pages.

  • Page Fetching — Convert web pages to Markdown for easy analysis
  • Link Extraction — Extract and analyze links from web pages
  • Site Crawling — Recursively crawl websites to discover content
  • Link Checking — Identify broken links on web pages
  • Pattern Matching — Find URLs matching specific patterns
  • Sitemap Generation — Generate XML sitemaps for websites

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Webscan is connected, these are the calls the assistant has available:

  • Parameters — - url (required): URL of the page to fetch
  • Prerequisites — The Prerequisites tool exposed by this server
  • Building — The Building tool exposed by this server

Configuration and credentials

You will need 2 environment variables: LOG_LEVEL, OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js >= 18 - npm

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the webscan mcp server does with a few real requests.

Choosing this one

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Webscan's toolset — Parameters, Prerequisites, Building — is a fair guide to whether it matches your workflow. It is maintained by bsmi021; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Webscan's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Parameters- url (required): URL of the page to fetch.
PrerequisitesThe Prerequisites tool exposed by this server.
BuildingThe Building tool exposed by this server.

How to install the Webscan MCP server

{
  "mcpServers": {
    "webscan": {
      "command": "node",
      "args": ["path/to/mcp-server-webscan/build/index.js"], // Corrected path
      "env": {
        "NODE_ENV": "development",
        "LOG_LEVEL": "info" // Example: Set log level via env var
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= 18 - npm
VariableDescriptionRequired
LOG_LEVELConfiguration value read at startup.Optional
OPENAI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Webscan to Parameters.
  • Use Webscan to Prerequisites.
  • Use Webscan to Building.

Frequently asked questions

It connects Webscan to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Parameters, Prerequisites, Building) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Webscan directly.