Cyber Lens AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_accountA | Connect your CyberLens account to this MCP server. Opens your browser to cyberlensai.com where you can sign up for free or log in. After authorizing, your API key is securely saved locally. Free accounts get 5 scans/month. No credit card required. If you already have an API key, you can also set the CYBERLENS_API_KEY environment variable instead. Cloud tools can also launch this flow automatically the first time repository or account-only tools need an account. |
| get_account_quotaA | Get your CyberLens account quota and remaining cloud scans. Returns:
Use this to confirm your account is connected and check how many cloud scans remain. If no account is connected yet, the MCP server will launch the CyberLens browser flow automatically before checking quota. |
| scan_claw_skillA | Scan an Open CLAW skill or plugin from CLAUDE Hub before installation. Runs locally in the MCP server and understands CLAW skill packaging, manifest permissions, and AI agent security models. Performs comprehensive security analysis on:
Checks for:
Use this BEFORE installing any CLAW skill to ensure it's safe for your environment. Examples:
|
| scan_websiteA | Scan a website for security vulnerabilities with a local quick mode and a full cloud mode. Without a connected account, the MCP server runs a local quick scan immediately. That local mode covers roughly 15 core checks such as HTTPS, security headers, basic form issues, inline scripts, and server disclosure. With a connected account, CyberLens starts the full cloud scan with 70+ checks. That path returns a scan ID you can use with get_scan_results. If cloud website quota is exhausted, CyberLens falls back to the local quick scan automatically and opens the upgrade page. |
| scan_repositoryA | Scan a public repository for secrets, dependency risks, and suspicious code patterns. Uses the live CyberLens cloud repository scanner for:
Checks for:
Returns a scan ID that can be used with get_scan_results to retrieve findings. If no account is connected yet, the MCP server will open the CyberLens browser flow automatically and then continue the scan. |
| get_scan_resultsA | Retrieve detailed findings from a completed security scan. Returns:
Use this after initiating a full cloud scan with scan_website or scan_repository. Local quick website scans return findings immediately and do not produce a scan ID. If no account is connected yet, the MCP server will connect first and then retrieve the cloud scan result. |
| get_security_scoreA | Get a quick security rating for a website. Returns:
Without an account, this uses the local quick website scanner. With an account, this uses the full CyberLens cloud path. If cloud website quota is exhausted, CyberLens falls back to the local quick score automatically. |
| get_remediation_guideA | Get detailed remediation guidance for a specific vulnerability or CWE. Returns:
Uses a built-in local guide library, so it still works even when no cloud guidance endpoint is available. |
| get_scan_transparencyA | Get an honest transparency report for this MCP server. Returns:
Use this to understand exactly what this server checks locally and which cloud features are live. |
| validate_claw_skillA | Validate a CLAW skill manifest and configuration for security best practices. Checks:
Use this before publishing a skill to CLAUDE Hub or for CI/CD validation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shadoprizm/cyberlens-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server