Skip to main content
mcpSource-backedReview first Safety Privacy

BoolsAI Scan MCP Server for Claude

BoolsAI hosted MCP server with no authentication required for tech stack scanning via boolsai_scan and boolsai_scan_paths tools on boolsai.ai/mcp.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • boolsai_scan fetches live websites and may trigger WAF or rate limits on target hosts.
  • Scanning third-party sites without permission may violate terms of service or security policies.
  • Detected stack data is heuristic and may include false positives or miss obfuscated technologies.
  • Do not use scan output as the sole input for security assessments or compliance audits.

Privacy notes

  • URLs and path lists you submit are sent to Boolsai.ai for analysis and may be logged for abuse prevention.
  • Local path scans depend on your MCP client; path names may reveal internal project structure if shared in chat.
  • Scan results can expose framework versions useful to attackers; handle reports as sensitive in competitive contexts.

Prerequisites

  • Claude Pro, Team, or Enterprise with Connectors support, or Claude Code with HTTP MCP transport.
  • Public URLs to scan or local project paths exposed through your MCP client's file access model.
  • Permission to probe target websites; avoid scanning systems you do not own without authorization.
  • Internet access so BoolsAI can fetch remote pages for stack detection.

Schema details

Install type
cli
Reading time
4 min
Difficulty score
20
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "boolsai": {
      "url": "https://boolsai.ai/mcp",
      "type": "http"
    }
  }
}

About this resource

Overview

BoolsAI Scan provides a hosted Model Context Protocol server for detecting technologies used on websites and in project paths. No authentication is required. Tools include boolsai_scan for URL-based detection and boolsai_scan_paths for path-oriented analysis.

Source and documentation are in Boolsai-ai/mcp. The endpoint is https://boolsai.ai/mcp.

Features

  • boolsai_scan detects CMS, frameworks, analytics, and hosting signals from URLs.
  • boolsai_scan_paths inspects technology markers from supplied path lists.
  • No API key or OAuth required for basic scanning.
  • Hosted remote HTTP transport at boolsai.ai/mcp.
  • Fast setup for competitive research and due diligence workflows.

Use Cases

  • Identify the CMS and JS framework on a prospect’s marketing site.
  • Compare tech stacks across competitor landing pages.
  • Pre-qualify integration partners by detecting API gateways and clouds.
  • Document stack assumptions before a migration proposal.
  • Batch-scan a list of URLs during market mapping.

Installation

Claude (Connectors)

  1. Add a custom connector under Settings → Connectors.
  2. Enter the MCP URL: https://boolsai.ai/mcp.
  3. Enable the connector; no API key is needed.
  4. Invoke scan tools from chat.

Claude Code

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

Other MCP clients

Add a remote HTTP connector pointing at https://boolsai.ai/mcp.

Configuration

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

No headers or environment variables are required.

Examples

Scan a website

Run boolsai_scan on https://example.com and list detected frameworks and analytics tools.

Compare competitors

Scan https://competitor-a.com and https://competitor-b.com and compare their tech stacks.

Path-based scan

Use boolsai_scan_paths on our repo’s package.json and config files to summarise the stack.

Security

  • Scan only sites you are authorised to probe.
  • Treat version fingerprints as sensitive when disclosing externally.
  • Confirm findings manually before security or compliance decisions.

Troubleshooting

Scan blocked or empty

The target may block bots or require JavaScript rendering; try the canonical HTTPS URL without redirects.

False positives

Heuristic detection can mislabel CDNs or tag managers; corroborate with manual inspection.

Rate limits

Space out bulk scans; excessive requests to the same domain may be throttled by BoolsAI or the target.

Path scan errors

Ensure paths exist and your client can read them; remote MCP path scans depend on local file access configuration.

Source citations

Add this badge to your README

Show that BoolsAI Scan MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/boolsai-scan-mcp-server.svg)](https://heyclau.de/entry/mcp/boolsai-scan-mcp-server)

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.