# ScanLabsAI Security Scanner (remote · scanlabsai.com)

Scan a website for vulnerabilities: OWASP Top 10, CVEs, SSL, headers - with plain-English fixes

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `scanlabsai.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp.md), [page](https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp)
- npm · `@scanlabsai/mcp-server`: 34/100, [markdown](https://verifymcp.io/servers/com-scanlabsai-scanner/scanlabsai-mcp-server.md), [page](https://verifymcp.io/servers/com-scanlabsai-scanner/scanlabsai-mcp-server)

## Channel facts

- Endpoint: `https://scanlabsai.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 997 tokens (~124/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the ScanLabsAI Security Scanner MCP server?

ScanLabsAI Security Scanner is a hosted endpoint at https://scanlabsai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-scanlabsai-scanner 'https://scanlabsai.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-scanlabsai-scanner": {
      "url": "https://scanlabsai.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-scanlabsai-scanner": {
      "type": "http",
      "url": "https://scanlabsai.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-scanlabsai-scanner]
url = "https://scanlabsai.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-scanlabsai-scanner": {
      "type": "remote",
      "url": "https://scanlabsai.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-scanlabsai-scanner --url 'https://scanlabsai.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-scanlabsai-scanner:
    url: "https://scanlabsai.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-scanlabsai-scanner": {
      "Transport": "http",
      "Url": "https://scanlabsai.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-scanlabsai-scanner -t streamable-http -u 'https://scanlabsai.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-scanlabsai-scanner": {
      "type": "http",
      "url": "https://scanlabsai.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-06 (score 80, 0)

- [security] Stability: 0.97 → pass

### 2026-09-05 (score 80, +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.

### 2026-09-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 76, +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.

### 2026-08-26 (score 75, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-24 (score 73, +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.

## MCP tools (8)

### `scan_website` (~140 tokens)

Run a ScanLabsAI security scan against a website and return a full Markdown vulnerability report (grouped by severity, with descriptions and remediation) that you can analyse, act on, and the user can save as security-report.md. Checks OWASP Top 10, CVEs, SSL/TLS, security headers and DNS. Use deep=true for a comprehensive scan (40,000+ vectors, slower). Only scan sites the user is authorised to test.

Input parameters:

- `deep` (boolean): Run a deep scan (comprehensive, slower). Defaults to false.
- `url` (string, required): The website URL to scan, e.g. https://example.com

### `scan_agent` (~283 tokens)

Red-team an AI agent for security weaknesses — prompt injection, system-prompt leakage, sensitive-data disclosure, unsafe output handling and excessive agency — mapped to the OWASP LLM Top 10, and return a Markdown report. This is agent-to-agent scanning: use it to assess another agent from here. Two target kinds are supported: kind="openai" for an OpenAI-compatible chat-completions endpoint, or kind="mcp" for an MCP server (its tool manifest is audited for tool-poisoning and over-broad capabilities). Requires a ScanLabsAI API key in the connection; each agent scan uses 5 AI credits. Probing is active and adversarial — only scan agents you own or are authorised to test.

Input parameters:

- `apiKey` (string): Optional bearer token / API key the target agent requires. Sent to the target only; not stored.
- `deep` (boolean): Run deeper probes (jailbreak + resource-exhaustion). Defaults to false.
- `endpoint` (string, required): The agent endpoint URL (chat-completions URL, or MCP server URL).
- `kind` (string, required): Target type: "openai" for a chat-completions endpoint, "mcp" for an MCP server.
- `model` (string): Model name for OpenAI-compatible endpoints, e.g. gpt-4o-mini.

### `compliance_report` (~126 tokens)

Generate a website compliance report — the same automated assessment the ScanLabsAI agency portal runs — covering GDPR/CCPA privacy, WCAG 2.1 AA accessibility, PCI DSS 4.0 payment security and general standards. Returns an overall score, per-category scores and the failing/at-risk checks with recommendations, as Markdown. Requires a ScanLabsAI API key in the connection; costs 1 AI credit per report. Only run against sites you are authorised to assess.

Input parameters:

- `url` (string, required): The website URL to assess for compliance, e.g. https://example.com

### `get_fix_guidance` (~70 tokens)

Get detailed, step-by-step remediation guidance for a specific vulnerability or security issue (e.g. "missing Content-Security-Policy header", "SQL injection", a CVE id). Returns actionable fixes.

Input parameters:

- `issue` (string, required): The vulnerability, finding title, or CVE id to fix.

### `lookup_cves` (~73 tokens)

Look up recent CVEs from the NIST NVD feed, optionally filtered by keyword. Returns id, severity, score and summary.

Input parameters:

- `keyword` (string): Optional keyword, e.g. "wordpress" or "openssl".
- `limit` (number): Max results (1-25). Defaults to 10.

### `get_pricing` (~26 tokens)

Get ScanLabsAI pricing: the free-first-scan policy and AI credit packs.

### `check_credits` (~51 tokens)

Check the signed-in account's AI credit balance. Requires a ScanLabsAI API key in the MCP connection (Authorization: Bearer slai_...). Create one at https://scanlabsai.com/mcp.

### `buy_credits` (~81 tokens)

Get a secure Stripe checkout link to buy an AI credit pack for the signed-in account. Requires a ScanLabsAI API key in the MCP connection. Credits are added automatically once payment completes. Packs: starter (5), pro (15), agency (50).

Input parameters:

- `pack` (string): Pack id: starter, pro, or agency. Defaults to pro.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp#diagnostics

## Score history

- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 73
- 2026-08-24: 73
- 2026-08-23: 72
- 2026-08-22: 72

## Common questions

### What is the ScanLabsAI Security Scanner MCP server?

ScanLabsAI Security Scanner is an MCP server listed in the public MCP registry as com.scanlabsai/scanner. Scan a website for vulnerabilities: OWASP Top 10, CVEs, SSL, headers - with plain-English fixes. This page covers its hosted endpoint (https://scanlabsai.com/api/mcp).

### Is the ScanLabsAI Security Scanner MCP server safe to use?

ScanLabsAI Security Scanner scores 80 out of 100 on VerifyMCP. 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 ScanLabsAI Security Scanner MCP server expose?

ScanLabsAI Security Scanner exposes 8 tools: scan_website, scan_agent, compliance_report, get_fix_guidance, lookup_cves, and 3 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.

### Does the ScanLabsAI Security Scanner MCP server require authentication?

No. We connected to ScanLabsAI Security Scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ScanLabsAI Security Scanner MCP server still maintained?

ScanLabsAI Security Scanner is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://scanlabsai.com/api/mcp
- Website: https://scanlabsai.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-scanlabsai-scanner/api-mcp