Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Quant-research MCP — tradeable signals from public-company website stack changes. 7 tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://signals.boolsai.ai/mcpRun this in your terminal
claude mcp add --transport http signals https://signals.boolsai.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"signals": {
"url": "https://signals.boolsai.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"signals": {
"type": "http",
"url": "https://signals.boolsai.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://signals.boolsai.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain boolsai.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
| Server | Connect URL | Tools | What it does |
|---|---|---|---|
| [Boolsai Scan](./boolsai-scan/server.json) | https://boolsai.ai/mcp | boolsai_scan, boolsai_scan_paths | Live 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 Directory](./boolsai-directory/server.json) | https://directory.boolsai.ai/mcp | summary, site_dossier, sites_using_vendor, lookup_id, brands_in_city, brands_in_market, stack_archetype, compare_sites, similar_sites, brands_by_founder | Pre-indexed directory of tens of thousands of ecommerce sites by vendor, account ID, country, founder, city, archetype. |
| [Boolsai Grep](./boolsai-grep/server.json) | https://grep.boolsai.ai/mcp | grep_pattern, count_pattern, sites_with_signal, list_signal_types | Parallel 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 Signals](./boolsai-signals/server.json) | https://signals.boolsai.ai/mcp | universe_summary, find_signals, test_filter, recent_events, event_dossier, scan_at_date, ticker_history | Quant-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).
initialize response includes a detailed instructions block — vendor recognition tips, output schemas, methodology. Agents don't have to guess.{
"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.
Settings → Connectors → Add custom connector → paste any of the four URLs above. Add all four for the full suite.
curl -sS https://boolsai.ai/mcp \
-H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq .
"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 })
┌──────────────────────────┐
│ 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.
See [PUBLISHING.md](./PUBLISHING.md) for the one-time DNS verification + per-server publish commands.
MIT — see LICENSE.
Built by Boolsai · Contact: founder@boolsai.ai