Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Boolsai Grep

Boolsai Grep

by ai.boolsai

Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://grep.boolsai.ai/mcp
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http ai.boolsai-grep https://grep.boolsai.ai/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "ai.boolsai-grep": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://grep.boolsai.ai/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.

Boolsai — MCP server suite

Stack-intelligence MCPs for AI agents. Live, no-auth, public access to every commerce site's tech stack — every vendor, every account ID, every inline script signature, plus a quant-research signal layer on top.

Built for AI agents doing competitive intel, agency prospect research, ecommerce due diligence, and ad-hoc commerce-data discovery.

This repo contains the Anthropic MCP Registry manifests for the four-server Boolsai suite. The actual servers live at *.boolsai.ai.


The four servers

ServerConnect URLToolsWhat it does
Boolsai Scanhttps://boolsai.ai/mcpboolsai_scan, boolsai_scan_pathsLive tech-stack scan of any public site. Returns every external host, inline script signature, route, vendor, account ID, and JSON-LD organisation block in one response.
Boolsai Directoryhttps://directory.boolsai.ai/mcpsummary, site_dossier, sites_using_vendor, lookup_id, brands_in_city, brands_in_market, stack_archetype, compare_sites, similar_sites, brands_by_founderPre-indexed directory of tens of thousands of ecommerce sites by vendor, account ID, country, founder, city, archetype.
Boolsai Grephttps://grep.boolsai.ai/mcpgrep_pattern, count_pattern, sites_with_signal, list_signal_typesParallel regex search across the R2 corpus of every scan we've ever taken. Use when a signal isn't pre-indexed — discover new vendor patterns, leaked account IDs, niche tracking pixels.
Boolsai Signalshttps://signals.boolsai.ai/mcpuniverse_summary, find_signals, test_filter, recent_events, event_dossier, scan_at_date, ticker_historyQuant-research MCP. Hunts for tradeable signals in 316 public-company website stack changes (1,761 events), SPY-benchmarked. Wayback Machine integration. Methodology baked into the initialize response.

Each server is independently published to the Anthropic MCP Registry under the ai.boolsai/* namespace (DNS-verified via boolsai.ai).


Why Boolsai

  • No auth, no key, no rate limit gymnastics. Paste a URL into Claude.ai → Settings → Connectors. Done.
  • First-party data. Every scan runs live on demand. No third-party feeds, no stale catalogue.
  • Built for AI consumption. Each server's initialize response includes a detailed instructions block — vendor recognition tips, output schemas, methodology. Agents don't have to guess.
  • Suite, not silo. Cross-discovery: each server's instructions reference the other three so agents can chain queries (scan → look up in directory → grep historical → test as signal).

Install

Claude Desktop / Claude Code / Cursor

{
  "mcpServers": {
    "boolsai-scan":      { "url": "https://boolsai.ai/mcp" },
    "boolsai-directory": { "url": "https://directory.boolsai.ai/mcp" },
    "boolsai-grep":      { "url": "https://grep.boolsai.ai/mcp" },
    "boolsai-signals":   { "url": "https://signals.boolsai.ai/mcp" }
  }
}

Restart the client. All four servers show up with their tools.

ChatGPT / Claude.ai Custom Connectors

Settings → Connectors → Add custom connector → paste any of the four URLs above. Add all four for the full suite.

One-liner test from a terminal

curl -sS https://boolsai.ai/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq .

Example agent prompts

"What's the full tech stack of gymshark.com?" → boolsai_scan({ url: "https://gymshark.com" })

"List ten stores using Klaviyo with their company IDs." → boolsai-directory.sites_using_vendor({ vendor: "klaviyo" })

"Show me sites with window._fs_org (FullStory) in their inline scripts." → boolsai-grep.sites_with_signal({ pattern: "window._fs_org" })

"Find the highest-α tradeable signal in the last 30 days with n ≥ 20." → boolsai-signals.find_signals({ horizon_days: 30, min_n: 20 })


Architecture

                   ┌──────────────────────────┐
                   │  AI agent (Claude / etc) │
                   └────────────┬─────────────┘
                                │ JSON-RPC 2.0 (Streamable HTTP)
            ┌───────────────────┼─────────────────────┐
            ▼                   ▼                     ▼
   boolsai.ai/mcp     directory.boolsai.ai/mcp   grep.boolsai.ai/mcp
   (live scanner)     (indexed corpus query)     (raw R2 search)
            │                   │                     │
            │                   │                     │
            ▼                   ▼                     ▼
     ┌──────────────────────────────────────────────────────┐
     │  R2 corpus (hundreds of thousands of historical scans) │
     └──────────────────────────────────────────────────────┘
                                ▲
                                │ derived
                signals.boolsai.ai/mcp  (quant signals from stack changes)

All four servers run on Cloudflare Workers with R2 for the historical corpus.


Publishing to the MCP Registry

See PUBLISHING.md for the one-time DNS verification + per-server publish commands.


License

MIT — see LICENSE.

Built by Boolsai · Contact: [email protected]

How do I install Boolsai Grep?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Boolsai Grep need an API key?
No required environment variable is listed on this record.
What transport does Boolsai Grep use?
Boolsai Grep is reached over HTTP.
When was Boolsai Grep last checked?
Last checked 2026-10-16. Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA