ScanLabsAI Security Scanner
REMOTE · SCANLABSAI.COM · 2 COMPONENTS · SCANNED SEP 20
Scan a website for vulnerabilities: OWASP Top 10, CVEs, SSL, headers - with plain-English fixes
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · scanlabsai.com
claude mcp add --transport http com-scanlabsai-scanner 'https://scanlabsai.com/api/mcp'
{
"mcpServers": {
"com-scanlabsai-scanner": {
"url": "https://scanlabsai.com/api/mcp"
}
}
} {
"servers": {
"com-scanlabsai-scanner": {
"type": "http",
"url": "https://scanlabsai.com/api/mcp"
}
}
} [mcp_servers.com-scanlabsai-scanner] url = "https://scanlabsai.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-scanlabsai-scanner": {
"type": "remote",
"url": "https://scanlabsai.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-scanlabsai-scanner --url 'https://scanlabsai.com/api/mcp' --transport streamable-http
mcp_servers:
com-scanlabsai-scanner:
url: "https://scanlabsai.com/api/mcp" {
"McpServers": {
"com-scanlabsai-scanner": {
"Transport": "http",
"Url": "https://scanlabsai.com/api/mcp"
}
}
} assistant mcp add com-scanlabsai-scanner -t streamable-http -u 'https://scanlabsai.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +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.
- 3 Sept 26 +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.
- 1 Sept 26 +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.
- 30 Aug 26 +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.
- 27 Aug 26 +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.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://scanlabsai.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scanlabsai.com | CN=WR3,O=Google Trust Services,C=US | 2 Aug 2026 | 31 Oct 2026 | RSA 2048 | SHA256-RSA | 45ce5d884511fd920a822119550aa588 |
| SANs: scanlabsai.com, www.scanlabsai.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of scanlabsai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| scanlabsai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://scanlabsai.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://scanlabsai.com/api/mcp | HTTPS enforced | 301 | https://scanlabsai.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buy_credits ~81
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).
| Name | Type | Req | Description |
|---|---|---|---|
| pack | string | – | Pack id: starter, pro, or agency. Defaults to pro. |
No output schema declared.
No examples provided.
check_credits ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compliance_report ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to assess for compliance, e.g. https://example.com |
No output schema declared.
No examples provided.
get_fix_guidance ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| issue | string | yes | The vulnerability, finding title, or CVE id to fix. |
No output schema declared.
No examples provided.
get_pricing ~26
Get ScanLabsAI pricing: the free-first-scan policy and AI credit packs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_cves ~73
Look up recent CVEs from the NIST NVD feed, optionally filtered by keyword. Returns id, severity, score and summary.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Optional keyword, e.g. "wordpress" or "openssl". |
| limit | number | – | Max results (1-25). Defaults to 10. |
No output schema declared.
No examples provided.
scan_agent ~283
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The agent endpoint URL (chat-completions URL, or MCP server URL). |
| kind | string | yes | 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. |
No output schema declared.
No examples provided.
scan_website ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Run a deep scan (comprehensive, slower). Defaults to false. |
| url | string | yes | The website URL to scan, e.g. https://example.com |
No output schema declared.
No examples provided.
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.