Boolsai Grep
REMOTE · GREP.BOOLSAI.AI · SCANNED AUG 3
Parallel regex across all Boolsai scans — discover new vendor patterns, niche signals. 4 tools.
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability47
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · grep.boolsai.ai
claude mcp add --transport http ai-boolsai-grep https://grep.boolsai.ai/mcp
[mcp_servers.ai-boolsai-grep] url = "https://grep.boolsai.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-boolsai-grep": {
"type": "remote",
"url": "https://grep.boolsai.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-boolsai-grep --url https://grep.boolsai.ai/mcp --transport streamable-http
mcp_servers:
ai-boolsai-grep:
url: "https://grep.boolsai.ai/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://grep.boolsai.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=boolsai.ai | CN=WE1,O=Google Trust Services,C=US | 12 Jul 2026 | 10 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | b9e3374367afc4020e31725d27ddd615 |
| SANs: boolsai.ai, grep.boolsai.ai, *.grep.boolsai.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of grep.boolsai.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| boolsai.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://grep.boolsai.ai/mcp | Verified | 200 | |
| http (plaintext) | http://grep.boolsai.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
count_pattern ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | — | — |
| domain_like | string | — | — |
| max_scan | integer | — | — |
| pattern | string | yes | — |
| since | string | — | — |
| tld | string | — | — |
| vendor | string | — | — |
No output schema declared.
No examples provided.
grep_pattern ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
list_signal_types ~33
Returns the full catalog of signal_types currently present in id_index, with counts of unique values and unique domains for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sites_with_signal ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| signal_type | string | yes | 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. |
No output schema declared.
No examples provided.