# scanbase-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** ru.scanbase
- **License:** MIT
- **npm:** scanbase-mcp
- **Source:** https://scanbase.ru/api/
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 7 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-06T00:46:17.078Z
- **Version scanned:** 1.1.0
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_site`
- `get_scan` — 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 s
- `list_scans` — 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
- `list_checks` — 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 Ru
- `account` — ScanBase account status for the configured API key: tier (free/package/subscription), remaining scan quota and reset time. Call before large scan batches or whe

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"scanbase\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"scanbase-mcp\"\n      ],\n      \"env\": {\n        \"SCANBASE_API_KEY\": \"<YOUR_SCANBASE_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `SCANBASE_API_KEY` — Scanbase API Key (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/scanbase-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/scanbase-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/scanbase-mcp
- HTML page: https://forgeregistry.com/registry/scanbase-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.