ru.scanbase/scanbase
NPM · SCANBASE-MCP
Website compliance checks for Russian personal data law 152-FZ: score, violations, fix instructions.
Available components
Last scanned (3 hours ago)
Scores higher than 38% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/scanbase-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account ~62
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. // Статус аккаунта: тариф и остаток квоты сканов.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_scan ~101
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 — перечитать находки, не тратя новый скан.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | scan_id (uuid) из результата scan_site или list_scans |
No output schema declared.
No examples provided.
list_checks ~101
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. // Справочник всех проверок (статья закона, штраф) — чтобы строить сайт сразу правильно, не тратя скан.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scans ~113
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, сравнить динамику балла.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Страница (по умолчанию 1) |
| per_page | integer | – | Размер страницы, ≤50 (по умолчанию 20) |
No output schema declared.
No examples provided.
scan_site ~240
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-ФЗ: балл, нарушения со штрафами, инструкции «как исправить» для правок кода.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Полный URL сайта, напр. https://example.ru/ |
| wait | boolean | – | Дождаться результата для тяжёлого сайта (по умолчанию true). Если false — вернёт статус pending, результат позже через list_scans/get_scan. |
No output schema declared.
No examples provided.
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.
npm · scanbase-mcp
claude mcp add ru-scanbase-scanbase -- npx -y scanbase-mcp
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.