Is the Boolsai Scan MCP server down?

mcp-registry/ai.boolsai/scan · v1.0.0

up · requires sign-in
Last checked 2026-10-23 14:15 UTC · handshake 581ms

As of 2026-10-23 14:15 UTC, the Boolsai Scan MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6.1 hours.

uptime (30d checks)
100%
checks observed
507
outages (90d)
6
tools
2

Live tech-stack scan of any public site — vendors, account IDs, scripts, JSON-LD. 2 tools.

Install Boolsai Scan MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http boolsai-scan-mcp-server https://boolsai.ai/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "boolsai-scan-mcp-server": {
      "type": "http",
      "url": "https://boolsai.ai/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

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

What to fix (3)

2 of 2 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: boolsai_scan, boolsai_scan_paths

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 →

Requires authentication; tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

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/ai.boolsai/scan"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.boolsai/scan"}) 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%2Fai.boolsai%2Fscan.svg)](https://glimind.com/server/mcp-registry%2Fai.boolsai%2Fscan?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.boolsai%2Fscan?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.boolsai%2Fscan.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.boolsai%2Fscan.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.boolsai%2Fscan?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:d7d0911d7cb5b6e2…, first seen 2026-10-17, included at leaf 4100 of 52,572. Version history · verify what your client received.

Tools (2)

Compare: most reliable web 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 Boolsai Scan MCP server down right now?

As of 2026-10-23 14:15 UTC, the Boolsai Scan MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6.1 hours.

How many tools does Boolsai Scan MCP server provide?

Boolsai Scan MCP server advertises 2 tools, including boolsai_scan, boolsai_scan_paths.

How do I install Boolsai Scan MCP server?

Point your MCP client at this streamable-http endpoint: https://boolsai.ai/mcp

Is the Boolsai Scan MCP server safe to connect to an AI agent?

Glimind scanned all 2 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 Boolsai Scan 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.

Feedback
Help us improve