# Urlscan Io (npm · @pipeworx/mcp-urlscan-io)

urlscan.io MCP.

- Trust score: 76/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 86/100, [markdown](https://verifymcp.io/servers/pipeworx-io-urlscan-io/urlscan-io-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-urlscan-io/urlscan-io-mcp)
- npm · `@pipeworx/mcp-urlscan-io`: 76/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io.md), [page](https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-urlscan-io`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-urlscan-io).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 386 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 15% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Urlscan Io MCP server?

Urlscan Io runs locally as an npm package, launched with npx -y @pipeworx/mcp-urlscan-io. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-urlscan-io -- npx -y @pipeworx/mcp-urlscan-io
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-urlscan-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-urlscan-io"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-urlscan-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-urlscan-io"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-urlscan-io -- npx -y @pipeworx/mcp-urlscan-io
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-urlscan-io": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-urlscan-io"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-urlscan-io --command npx --arg -y --arg @pipeworx/mcp-urlscan-io
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-urlscan-io:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-urlscan-io"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-urlscan-io": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-urlscan-io"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-urlscan-io -t stdio -c npx -a -y @pipeworx/mcp-urlscan-io
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-urlscan-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-urlscan-io"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 76, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 76)

First indexed and scored.

## MCP tools (5)

### `search` (~127 tokens)

Search the public urlscan.io archive of website scans using urlscan query syntax, for example page.domain:example.com, task.url, ip, asn, or filename terms, with size and search_after paging and no API key needed. Returns matching scan records with the scanned URL, page domain, IP, ASN, server, scan date, and the scan uuid used to pull the full report. Answers which pages urlscan has already scanned for a domain, brand, or infrastructure indicator.

Input parameters:

- `query` (string, required)
- `search_after` (string)
- `size` (number)

### `result` (~23 tokens)

Full result by scan uuid (keyless).

Input parameters:

- `uuid` (string, required)

### `submit` (~90 tokens)

Submit a new URL for scanning (requires key).

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 of scan country.
- `customagent` (string)
- `referer` (string)
- `tags` (array)
- `url` (string, required)
- `useragent` (string)
- `visibility` (string): public (default) | unlisted | private

### `domain` (~46 tokens)

Search urlscan.io past scan results for a specific domain (no API key required); returns scan records including URL, verdict, screenshot link, and scan date.

Input parameters:

- `domain` (string, required)

### `ip` (~44 tokens)

Search urlscan.io past scan results for a specific IP address (no API key required); returns scan records for pages hosted at or contacting that IP.

Input parameters:

- `ip` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 76

## Common questions

### What is the Urlscan Io MCP server?

Urlscan Io is an MCP server listed in the public MCP registry as io.github.pipeworx-io/urlscan-io. urlscan.io MCP. This page covers its npm package (@pipeworx/mcp-urlscan-io).

### Is the Urlscan Io MCP server safe to use?

Urlscan Io scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Urlscan Io MCP server expose?

Urlscan Io exposes 5 tools: search, result, submit, domain, ip. Their descriptions and schemas cost roughly 330 tokens of context every time the server is loaded.

### Is the Urlscan Io MCP server still maintained?

Urlscan Io is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Urlscan Io MCP server under?

Urlscan Io declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-urlscan-io
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-urlscan-io
- Repository: https://github.com/pipeworx-io/mcp-urlscan-io
- Website: https://pipeworx.io/packs/urlscan-io
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-urlscan-io/pipeworx-mcp-urlscan-io