Boolsai Grep MCP Server

by boolsai Your server? Claim it

not responding

Boolsai Grep is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 19 May 2026.

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

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

49 ms

Response time

average over 24h

Stars

last commit 19 May 2026

Boolsai Grep does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://grep.boolsai.ai/mcp

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "grep": {
      "url": "https://grep.boolsai.ai/mcp"
    }
  }
}

.vscode/mcp.json

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

count

count_pattern

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.

grep

grep_pattern

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.

signal

list_signal_types

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

sites

sites_with_signal

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.

Endpoints

URL	Transport	State	Latency	Checked
https://grep.boolsai.ai/mcp	streamable-http	answering	49 ms	12 min ago

Alternatives to Boolsai Grep

same job, measured the same way

Toolcairn MCP

by neurynae

MCP server for tool discovery: find, compare, and verify tools across 35+ registries.

69 installs/wk local only

Fx Signal

by airblockfz

FX bottom/top signals: 48 pairs (USD/KRW base), verdict + score, scans. Pay-per-call x402.

5 tools answering

Coin Signal

by airblockfz

Crypto bottom/top signals: verdict + score per coin, market scans. Pay-per-call x402.

6 tools answering

Stock Signal Kr

by airblockfz

Korea stock (KOSPI/KOSDAQ) bottom/top signals: verdict + score, scans. Pay-per-call x402.

5 tools answering

Commodity Signal

by airblockfz

Commodity futures bottom/top signals: 28 futures, verdict + score, scans. Pay-per-call x402.

6 tools answering

Interline

by choppaaahh

Neutral, non-custodial MCP payment router: discover rails, then pay across them.

66 installs/wk local only

Stock Signal Us

by airblockfz

US stock bottom/top signals: S&P500 + indexes, verdict + score, scans. Pay-per-call x402.

5 tools answering

Routavo

by routavo

Any API, four tools: discover, call with routing and signed receipts, verify, dispute.

4 tools answering

Boolsai Grep — questions

Answers built from our own checks of this server.

What can Boolsai Grep do?

It exposes 4 tools, read directly from the server on our last check. Among them: count_pattern, grep_pattern, list_signal_types, sites_with_signal. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Boolsai Grep working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 49 ms. The bar chart above shows every period we have measured.

The registry lists Boolsai Grep as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Boolsai Grep?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Boolsai Grep need an API key?

No. Boolsai Grep completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

Is Boolsai Grep open source?

The code is open source: it is published under the MIT licence, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at grep.boolsai.ai, which runs on its operator's own terms.