Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Boolsai Grep

REMOTE · GREP.BOOLSAI.AI

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

Available components

−69 this week 0 Trust /100

Last scanned (49 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 26 Sep 2026.

Category Search and Retrieval

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • HTTPS
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Oct 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 2 Oct 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 1 Oct 26 −13

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 30 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 29 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 28 Sept 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
  • 27 Sept 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HTTPS: fail → pass ▲ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 25 Sept 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
Diagnostics

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 Oct 2026 · Probed https://grep.boolsai.ai/mcp

TLS unreached
DNSSEC inconclusive

Validation of grep.boolsai.ai. — Inconclusive

Zone DS Keys Algorithms Outcome
grep.boolsai.ai. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://grep.boolsai.ai/mcp Unreachable
http (plaintext) http://grep.boolsai.ai/mcp HTTPS enforced
MCP tools · 4 exposed · ~617 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
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.

NameTypeReqDescription
case_sensitiveboolean––
domain_likestring––
max_scaninteger––
patternstringyes–
sincestring––
tldstring––
vendorstring––

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.

NameTypeReqDescription
allboolean–Scan ALL shards — entire corpus. May exceed Worker CPU budget for complex regex; use only when you've narrowed via vendor/tld.
case_sensitiveboolean–Default false
domain_likestring–Substring to match in domain, e.g. 'patagonia'
limitinteger–Max matching sites to return (default 200, max 2000)
max_scaninteger–Max R2 objects to read for this query (default 10000, max 200000)
max_shardsinteger–Cap how many shards to query (newest-first). Default 100, raise to scan deeper history. Each shard ≈ 800 scans.
patternstringyesJavaScript regex (case-insensitive by default)
sincestring–Only scans >= this date, format YYYY-MM-DD
tldstring–Restrict to this TLD, e.g. 'com.au' or 'co.uk'
vendorstring–Pre-narrow via id_index to sites known to use this vendor (e.g. 'shopify')
with_snippetsboolean–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.

NameTypeReqDescription
limitinteger––
signal_typestringyesOne of the known signal_type values (see instructions)
signal_valuestring–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.

Install

How do I install the Boolsai Grep MCP server?

Boolsai Grep is a hosted endpoint at https://grep.boolsai.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · grep.boolsai.ai

# add to Claude Code
claude mcp add --transport http ai-boolsai-grep 'https://grep.boolsai.ai/mcp'
Common questions

What is the Boolsai Grep MCP server?

Boolsai Grep is an MCP server listed in the public MCP registry as ai.boolsai/grep. Parallel regex across all Boolsai scans, discover new vendor patterns, niche signals. 4 tools. This page covers its hosted endpoint (https://grep.boolsai.ai/mcp).

Is the Boolsai Grep MCP server safe to use?

Boolsai Grep scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Boolsai Grep MCP server expose?

Boolsai Grep exposes 4 tools: grep_pattern, count_pattern, sites_with_signal, list_signal_types. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

Does the Boolsai Grep MCP server require authentication?

Its publisher declares no required credentials for Boolsai Grep. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Boolsai Grep MCP server still maintained?

Boolsai Grep has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Boolsai Grep MCP server?

VerifyMCP ran 2 checks on Boolsai Grep, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about Boolsai Grep: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.