Is the Scanlabsai Scanner MCP server down?

mcp-registry/com.scanlabsai/scanner · v1.0.0

healthy
Last checked 2026-10-18 12:10 UTC · handshake 134ms

As of 2026-10-18 12:10 UTC, the Scanlabsai Scanner MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.9%
checks observed
3,697
outages (90d)
10
tools
8

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

Install Scanlabsai Scanner MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http scanlabsai-scanner-mcp-server https://scanlabsai.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 8 tool(s); ~1,178 tokens of tool definitions.
Scores higher than 40% of 15,358 MCP servers Glimind has audited.
Its tool list costs an agent ~1,178 tokens per session — lighter than 70% of servers.
82 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints10
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: buy_credits, check_credits, compliance_report, get_fix_guidance, get_pricing and 3 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: buy_credits

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.scanlabsai%2Fscanner/fixes

buy_credits 1 change
{
  "name": "buy_credits",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "pack": {
        "type": "string",
        "description": "Pack id: starter, pro, or agency. Defaults to pro."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
check_credits 1 change
{
  "name": "check_credits",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_fix_guidance 1 change
{
  "name": "get_fix_guidance",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "issue"
    ],
    "properties": {
      "issue": {
        "type": "string",
        "description": "The vulnerability, finding title, or CVE id to fix."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.scanlabsai/scanner"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.scanlabsai/scanner"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.scanlabsai%2Fscanner.svg)](https://glimind.com/server/mcp-registry%2Fcom.scanlabsai%2Fscanner?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.scanlabsai%2Fscanner?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.scanlabsai%2Fscanner.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.scanlabsai%2Fscanner.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.scanlabsai%2Fscanner?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a7d0d8b33d6263b8…, first seen 2026-10-17, included at leaf 8078 of 21,795. Version history · verify what your client received.

Tools (8)

Compare: most reliable payments servers · most reliable other servers · most reliable security servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Scanlabsai Scanner MCP server down right now?

As of 2026-10-18 12:10 UTC, the Scanlabsai Scanner MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Scanlabsai Scanner MCP server provide?

Scanlabsai Scanner MCP server advertises 8 tools, including buy_credits, check_credits, compliance_report, get_fix_guidance, get_pricing.

How do I install Scanlabsai Scanner MCP server?

Point your MCP client at this streamable-http endpoint: https://scanlabsai.com/api/mcp

Is the Scanlabsai Scanner MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Scanlabsai Scanner MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.