Log inSubmit server
CyberLens logo

CyberLens

Scan websites, public repositories, and Open CLAW skills for security findings through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install CyberLens

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cyberlens": {
      "command": "npx",
      "args": [
        "-y",
        "@shadoprizm/cyberlens-mcp-server"
      ],
      "env": {
        "CYBERLENS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly (6d ago).

Overview

CyberLens MCP server gives AI assistants tools for scanning websites, public repositories, and Open CLAW skill packages. It supports local website checks and skill analysis without an account, while connected accounts enable cloud website scans, repository scans, quota information, and detailed results. Use it when an agent needs to review a website, repository, or skill package before deployment or installation. The server runs through Node.js and can connect through browser-based account authentication or a configured API key.

Use cases

  • Scan a CLAW skill before installing it
  • Check a public repository for secrets and dependency issues
  • Run a quick website security review without an account
  • Retrieve findings from a completed cloud scan
  • Get remediation guidance for a vulnerability class

Key features

  • Open CLAW skill package scanning
  • Local and cloud website security scans
  • Public repository scanning
  • Browser-based account connection
  • Security scores and detailed findings
  • Local remediation playbooks

Tools10

What CyberLens lets your agent do. Expand a tool for its parameters.

Verified live~1.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

11/11 checks healthy over the last 61d

What it can do

From the 10 tools this server returned when we ran it.

Runs commands · 1Handles credentials · 3Makes network requests · 2Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age217 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @shadoprizm/cyberlens-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads138Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.

How CyberLens works

What CyberLens MCP server does

CyberLens MCP server exposes security analysis tools for AI assistants and agentic coding workflows. It can inspect websites, public repositories, and Open CLAW skills, then return scores, findings, and remediation guidance. The server supports local checks that do not require an account as well as cloud-backed scans available after account connection.

Skill analysis is designed for packages from CLAW Hub, direct skill download URLs, or supported skill ZIP files. The scanner examines package metadata and source files for issues such as hardcoded secrets, shell execution, unsafe deserialization, insecure requests, dangerous file operations, and unpinned dependencies. It also lists external URLs used by the package.

How it works

Website tools have two modes. A local quick scan runs without authentication and performs roughly 15 checks, including HTTPS, security headers, server disclosure, insecure forms, and inline-script indicators. A connected account enables the cloud scan path with more than 70 checks, scan history, and AI analysis. If website cloud quota is unavailable, the server falls back to the local scan rather than failing outright.

Repository scans use the cloud service and support public GitHub, GitLab, and Bitbucket repositories, along with supported ZIP targets. Cloud results can be retrieved after a scan completes. The get_scan_transparency tool reports which checks run locally and which endpoints use the live cloud service.

For account-required operations, CyberLens opens a browser flow at cyberlensai.com, receives a local callback, stores the API key in ~/.cyberlens/mcp/config.json, and retries the original request. An API key can also be supplied through the CYBERLENS_API_KEY environment variable. Free accounts include five scans per month, according to the project documentation.

Setup and configuration

The project requires Node.js 18 or newer. The documented package installation uses:

Terminal
npx -y @shadoprizm/cyberlens-mcp-server

For local development, clone the repository, run npm install, and build with npm run build. A source checkout can be started with Node against dist/index.js.

Claude Desktop uses an MCP configuration entry with npx and the package name. Claude Code uses its MCP settings or project configuration, while VS Code configures the server through the relevant Copilot or Continue MCP settings. Account connection is optional for local website scans, CLAW skill scanning, manifest validation, remediation guidance, and transparency information.

Tools and capabilities

The CyberLens MCP server provides these tool groups:

  • Account connection and quota inspection.
  • CLAW package scanning and manifest validation.
  • Local or cloud website scanning and security scoring.
  • Public repository scanning and cloud result retrieval.
  • Local remediation playbooks for common CWEs and vulnerability classes.
  • Reporting on local checks and cloud endpoints.

scan_claw_skill downloads and cleans up a temporary package before analysis. validate_claw_skill checks a skill manifest against security practices. get_remediation_guide supplies built-in fix guidance and code examples for supported vulnerability categories.

Limitations and notes

Local website scans do not provide the full cloud check set. Requests for a cloud-only website mode without an account are handled as local quick scans instead. Repository scanning requires an account and available cloud quota. Cloud scan history and richer website analysis also depend on account access.

Skill scanning runs locally and does not send the analyzed package to an external service. The API key is stored locally when browser authentication is used, so deployments should account for filesystem access and configuration persistence.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about CyberLens

CyberLens is an MCP server that connects AI assistants to local and cloud security scanning for websites, public repositories, and Open CLAW skills. Its main tools scan sites and repositories, analyze skill packages, validate manifests, retrieve cloud findings, report quotas, calculate scores, and provide remediation guidance.

Install it with `npx -y @shadoprizm/cyberlens-mcp-server`. For local development, clone the repository, run `npm install`, and build with `npm run build`. The project documents Node.js 18 or newer and provides configuration examples for MCP clients.

Yes, CyberLens works with Claude Desktop through its MCP server configuration. Add an entry that runs `npx` with `-y @shadoprizm/cyberlens-mcp-server`, using the Claude configuration file for macOS or Windows. A built local `dist/index.js` entry is also documented.

Yes, website scans and security scores can run in local quick mode without an account. This mode performs roughly 15 core checks and returns immediately. A connected account is needed for the full cloud scan, which provides more than 70 checks, history, and richer analysis.

Repository scans authenticate through a CyberLens account. If no account is connected, the server opens a browser flow, saves the resulting API key locally, and continues the original request. You can also provide `CYBERLENS_API_KEY` in the MCP configuration.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCyberLens AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/cyberlens?style=directory)](https://allmcps.com/mcp/cyberlens)
HTML Embed
<a href="https://allmcps.com/mcp/cyberlens"><img src="https://allmcps.com/api/badge/cyberlens?style=directory" alt="CyberLens on AllMCPs" /></a>