# ru.scanbase/scanbase (npm · scanbase-mcp)

Website compliance checks for Russian personal data law 152-FZ: score, violations, fix instructions.

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

## Components

- npm · `scanbase-mcp`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ru-scanbase-scanbase/scanbase-mcp.md), [page](https://verifymcp.io/servers/ru-scanbase-scanbase/scanbase-mcp)

## Channel facts

- Registry: `npm`
- Package: `scanbase-mcp`
- Version: `1.1.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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 35 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 849 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.

## Install

### How do I install the ru.scanbase/scanbase MCP server?

ru.scanbase/scanbase runs locally as an npm package, launched with npx -y scanbase-mcp. 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 ru-scanbase-scanbase -- npx -y scanbase-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ru-scanbase-scanbase": {
      "command": "npx",
      "args": [
        "-y",
        "scanbase-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ru-scanbase-scanbase": {
      "command": "npx",
      "args": [
        "-y",
        "scanbase-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ru-scanbase-scanbase -- npx -y scanbase-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ru-scanbase-scanbase --command npx --arg -y --arg scanbase-mcp
```

### Hermes

```yaml
mcp_servers:
  ru-scanbase-scanbase:
    command: "npx"
    args: ["-y", "scanbase-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ru-scanbase-scanbase": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "scanbase-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ru-scanbase-scanbase -t stdio -c npx -a -y scanbase-mcp
```

### Other

```json
{
  "mcpServers": {
    "ru-scanbase-scanbase": {
      "command": "npx",
      "args": [
        "-y",
        "scanbase-mcp"
      ]
    }
  }
}
```

## 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-11-05 (score 70, −3)

- [functional] Stability: pass → 0.77

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

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 71, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `scan_site` (~240 tokens)

Scan a LIVE website for compliance with the Russian personal data law 152-FZ and related laws (ads 38-FZ, recommender systems 408-FZ, education 273-FZ, medicine 323-FZ). Use when the user is launching/reviewing a site for the Russian market or asks about 152-ФЗ, персональные данные, privacy, cookies, согласие, Роскомнадзор. Returns a 0–100 compliance score, violations with potential fines (rubles), machine-actionable fix instructions to apply as code changes, and document/cookie/tracker analysis. The site must be publicly reachable (not localhost). After applying fixes, call scan_site again to verify. // Проверка живого сайта на 152-ФЗ: балл, нарушения со штрафами, инструкции «как исправить» для правок кода.

Input parameters:

- `url` (string, required): Полный URL сайта, напр. https://example.ru/
- `wait` (boolean): Дождаться результата для тяжёлого сайта (по умолчанию true). Если false — вернёт статус pending, результат позже через list_scans/get_scan.

### `get_scan` (~101 tokens)

Retrieve a previously saved ScanBase scan result by its scan_id (uuid from scan_site or list_scans). Use to re-read findings without spending a new scan. Only scans of this account; gated by the key's current tier. // Сохранённый результат скана по scan_id — перечитать находки, не тратя новый скан.

Input parameters:

- `scan_id` (string, required): scan_id (uuid) из результата scan_site или list_scans

### `list_scans` (~113 tokens)

List this account's ScanBase scan history (last ≤100): scan_id, url, domain, score, violations count, date. Use to find a past scan_id, compare scores over time, or check scans across multiple projects. // История сканов аккаунта: найти прошлый scan_id, сравнить динамику балла.

Input parameters:

- `page` (integer): Страница (по умолчанию 1)
- `per_page` (integer): Размер страницы, ≤50 (по умолчанию 20)

### `list_checks` (~101 tokens)

List all compliance checks ScanBase performs (currently ~45): id, name, category, law article, max fine in rubles. Call this BEFORE writing site code for the Russian market to build it compliant from the start, or to explain to the user what will be verified. Requires no scan and spends no quota. // Справочник всех проверок (статья закона, штраф) — чтобы строить сайт сразу правильно, не тратя скан.

### `account` (~62 tokens)

ScanBase account status for the configured API key: tier (free/package/subscription), remaining scan quota and reset time. Call before large scan batches or when a scan fails with a quota error. // Статус аккаунта: тариф и остаток квоты сканов.

## Diagnostics

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

## Score history

- 2026-11-05: 70
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 65
- 2026-10-11: 65
- 2026-10-04: 65
- 2026-10-03: 65
- 2026-10-02: 65
- 2026-10-01: 65

## Common questions

### What is the ru.scanbase/scanbase MCP server?

ru.scanbase/scanbase is an MCP server listed in the public MCP registry as ru.scanbase/scanbase. Website compliance checks for Russian personal data law 152-FZ: score, violations, fix instructions. This page covers its npm package (scanbase-mcp).

### Is the ru.scanbase/scanbase MCP server safe to use?

ru.scanbase/scanbase scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 ru.scanbase/scanbase MCP server expose?

ru.scanbase/scanbase exposes 5 tools: scan_site, get_scan, list_scans, list_checks, account. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Is the ru.scanbase/scanbase MCP server still maintained?

ru.scanbase/scanbase 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 ru.scanbase/scanbase MCP server under?

ru.scanbase/scanbase 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/scanbase-mcp
- Socket report: https://socket.dev/npm/package/scanbase-mcp
- Website: https://scanbase.ru/api/
- Changelog RSS feed: https://verifymcp.io/servers/ru-scanbase-scanbase/scanbase-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ru-scanbase-scanbase/scanbase-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ru-scanbase-scanbase/scanbase-mcp