# Boolsai Grep (remote · grep.boolsai.ai)

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

- Trust score: 54/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `grep.boolsai.ai`: 54/100 (this document), [markdown](https://verifymcp.io/servers/ai-boolsai-grep/grep.md), [page](https://verifymcp.io/servers/ai-boolsai-grep/grep)

## Channel facts

- Endpoint: `https://grep.boolsai.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 47/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1428 tokens (~357/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-boolsai-grep https://grep.boolsai.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-boolsai-grep]
url = "https://grep.boolsai.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-boolsai-grep": {
      "type": "remote",
      "url": "https://grep.boolsai.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-boolsai-grep --url https://grep.boolsai.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-boolsai-grep:
    url: "https://grep.boolsai.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-boolsai-grep": {
      "type": "http",
      "url": "https://grep.boolsai.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 52, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 51)

First indexed and scored.

## MCP tools (4)

### `grep_pattern` (~333 tokens)

Run a JavaScript regex across every scan we've ever taken. Returns matching site URLs (and optional snippets). Best for ad-hoc discovery of patterns NOT already extracted into id_index. Pass narrowing filters (vendor, tld, since) to keep scan volume manageable. Default returns URLs only — set with_snippets=true if you also want the matched JSON context.

Input parameters:

- `all` (boolean): Scan ALL shards — entire corpus. May exceed Worker CPU budget for complex regex; use only when you've narrowed via vendor/tld.
- `case_sensitive` (boolean): Default false
- `domain_like` (string): Substring to match in domain, e.g. 'patagonia'
- `limit` (integer): Max matching sites to return (default 200, max 2000)
- `max_scan` (integer): Max R2 objects to read for this query (default 10000, max 200000)
- `max_shards` (integer): Cap how many shards to query (newest-first). Default 100, raise to scan deeper history. Each shard ≈ 800 scans.
- `pattern` (string, required): JavaScript regex (case-insensitive by default)
- `since` (string): Only scans >= this date, format YYYY-MM-DD
- `tld` (string): Restrict to this TLD, e.g. 'com.au' or 'co.uk'
- `vendor` (string): Pre-narrow via id_index to sites known to use this vendor (e.g. 'shopify')
- `with_snippets` (boolean): Include matched JSON context. Default false (URLs only).

### `count_pattern` (~97 tokens)

Same as grep_pattern but returns only the count of matching sites. Faster — no per-match serialization. Useful for sizing 'how many sites use X' before doing a full grep.

Input parameters:

- `case_sensitive` (boolean)
- `domain_like` (string)
- `max_scan` (integer)
- `pattern` (string, required)
- `since` (string)
- `tld` (string)
- `vendor` (string)

### `sites_with_signal` (~154 tokens)

Return sites that have a known signal_type=signal_value pair in id_index. MUCH faster than grep_pattern — uses pre-indexed D1 lookup. Use this whenever the signal_type is in the list (see instructions). Examples: sites_with_signal(signal_type='vendor', signal_value='mparticle_workspace') ← won't work, that's an ID type, use sites_with_signal(signal_type='mparticle_workspace') WITHOUT signal_value to list all values + their domains.

Input parameters:

- `limit` (integer)
- `signal_type` (string, required): One of the known signal_type values (see instructions)
- `signal_value` (string): Optional exact value to filter to. If omitted, returns all domains for any value of this signal_type.

### `list_signal_types` (~33 tokens)

Returns the full catalog of signal_types currently present in id_index, with counts of unique values and unique domains for each.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-boolsai-grep/grep#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 53
- 2026-08-01: 53
- 2026-07-31: 52
- 2026-07-30: 52
- 2026-07-29: 53
- 2026-07-28: 53
- 2026-07-27: 52
- 2026-07-26: 51

## Links

- Remote endpoint: https://grep.boolsai.ai/mcp
- Repository: https://github.com/Boolsai-ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-boolsai-grep/grep/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-boolsai-grep/grep/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-boolsai-grep/grep