Urlscan Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

URL scanning from urlscan.io. No key required.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant scan URLs through urlscan.io without requiring an API key.

What you can do
Submit URLs to urlscan.io for scanning and retrieve the resulting scan information for an assistant to review. The manifest lists no individual tools, so the exact operations are not documented beyond URL scanning. It runs as a local process on the user's machine over stdio.
When to use it
Useful when you want an assistant to check a link or site through urlscan.io during a conversation, for example to look at what a URL resolves to or how it behaves, without setting up an API key first.
Requirements
A local runtime able to run the npm package urlscan-mcp (Node.js for an npm package), launched as a stdio process on the user's machine. No API key, environment variables or headers are declared. Network access to urlscan.io is implied by the scanning function.
Before you install
Submitted URLs are sent to urlscan.io, a third party, and may become publicly visible there; avoid scanning private, internal or sensitive links. The manifest declares no authentication, so any rate limits or terms of the service still apply. No tool list is published, so confirm what it sends before use.

Installation

In SourceWeft

  1. Open Urlscan Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.