Scanbase

ru.scanbasePublished by scanbase.ruv1.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Scanbase checks a website's compliance with Russian personal data law 152-FZ, returning a score, violations and fix instructions to an AI assistant.

What you can do
Run a compliance check of a website against Russian personal data law 152-FZ and get a compliance score back. Retrieve the violations found and the recommended fixes for each one. The manifest lists no individual tools, so the exact commands are not documented here.
When to use it
Useful when you need a quick compliance assessment of a Russian-facing website under 152-FZ, for example before launch or during an audit, and want the findings and remediation steps summarized in the assistant.
Requirements
Runs as a local process over stdio, installed from the npm package scanbase-mcp, so Node.js is needed. Requires a ScanBase API key supplied in the SCANBASE_API_KEY environment variable; a free key is obtained from the ScanBase account cabinet. Desktop client only.
Before you install
The API key is a secret sent to Scanbase's servers; keep it out of shared configuration. The site address you submit is sent to a third-party service, so avoid targets you cannot disclose. Results are an automated assessment, not legal advice.

Installation

In SourceWeft

  1. Open Scanbase 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.

Tools

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

Version history

1
  1. v1.1.0LatestSep 30, 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.