launch-detector-mcp
launch-detector-mcp
See what a company is building before they announce it. Every website needs a TLS certificate, and every certificate is published in public certificate transparency logs, usually weeks before a new subdomain goes live. This MCP server reads those logs through crt.sh and surfaces new product-like subdomains, so Claude (or any MCP client) can tell you what a competitor might be about to launch.
No API keys. One line to install.
You: Anything new brewing at Linear?
Claude: [launch_signals(domain="linear.app", days=365)]
• "orbit" is the strongest new name: orbit.linear.app and *.orbit.linear.app
first got certificates on 2026-08-24. A wildcard under it suggests
something that hosts many sub-sites.
• "checkout" (2026-06-29) and "asks" (2026-02-10) are also new.
These are hints from certificate logs, not announcements.Summarized from real tool output, 1 Oct 2026.

Why
You want to know | Without it | With launch-detector |
What a competitor is building | Wait for the press release |
|
Whether a rumored product is real | Guess |
|
When a company got busy | Nothing |
|
What changed across 5 rivals this month | Check each by hand |
|
Related MCP server: ctscout
How it works
flowchart LR
C[Claude / MCP client] -->|tool call| S[launch-detector-mcp]
S --> T[crt.sh: every certificate for *.domain]
T --> N[Hostnames with first/last seen dates]
N --> K["Stem: stt-a100.titanium.api.x.com → titanium<br/>drop regions, numbered nodes, mail/cdn/www"]
K --> R[Score: new + several hostnames + staging/beta/preview + product words]
R -->|ranked names with evidence| CStaging, beta, preview and sandbox variants are kept as signals, not dropped: a product that gets a staging host first is often close to launch. Results are cached for a day on disk (~/.cache/launch-detector).
Install
Requires uv.
Claude Code
claude mcp add launch-detector -- uvx launch-detector-mcpClaude Desktop / Cursor (claude_desktop_config.json / .cursor/mcp.json)
{
"mcpServers": {
"launch-detector": {
"command": "uvx",
"args": ["launch-detector-mcp"]
}
}
}Tools
Tool | What it does |
| New product-like names under a domain in the window, ranked, with the reasons and example hostnames |
| Raw evidence: every hostname first seen in the window, with its name and environment words |
| New hostnames per month and which product-like names appeared each month |
| Radar over 2–8 competitors: new hostnames and top signals per company |
| First/last certificate, count and issuers for one hostname |
Prompts: whats_coming (one company), competitor_radar (several companies).
Try these
"What might Stripe launch next? Use the last 6 months."
"Run a launch radar on openai.com, anthropic.com and mistral.ai for the last 30 days."
"When did Linear's certificate activity spike this year?"
Limits (read these)
Hints, not proof. A new hostname can be an internal tool, a test, a vendor integration or a renamed service.
Companies that use wildcard certificates (
*.example.com) for everything reveal less.crt.sh is a free community service: it is slow (20–60 s for big domains) and often busy; the server retries and caches, but sometimes you will need to try again.
Only public certificate data is used. Please use it for market research, not to probe systems.
Part of the keyless MCP series
Open-source MCP servers that answer one market question each, with public data and no API keys.
Server | Question it answers |
What do users hate about competitor apps and games? (App Store + Steam reviews) | |
How did a SaaS pricing page change over the years? (Wayback Machine) | |
Which skills are tech companies hiring for, and which are rising? (HN Who is hiring) | |
What does each LLM cost, and did it get cheaper? (OpenRouter + price history) | |
launch-detector-mcp (this one) | What is a company about to launch? (certificate transparency logs) |
Development
uv sync --extra dev
uv run pytest # offline tests with a mocked crt.sh
uv run python scripts/smoke_live.py # live check against crt.sh (a few minutes)
uv run --with rich python scripts/demo.py linear.app # terminal demo (vhs docs/demo.tape records the GIF)MIT © Ali Altunar
Available Tools
5 toolshostname_historyBRead-onlyIdempotent
When one hostname first and last got a certificate, how many, and from which issuers.
Inputs: hostname (required), response_format. Returns: result
launch_signalsBRead-onlyIdempotent
Product-like names that first appeared under a domain in the window, ranked by how much they look like an upcoming launch (new, several hostnames, staging/beta/preview variants, product words).
Inputs: domain (required), top, days, response_format. Returns: result
new_subdomainsBRead-onlyIdempotent
Raw evidence: every hostname whose first certificate appeared in the window, newest first, with its product-like name and environment words.
Inputs: domain (required), days, limit, response_format, +1 more. Returns: result
subdomain_timelineBRead-onlyIdempotent
New hostnames per month and the product-like names that first appeared each month. Bursts often line up with launches, rebrands or new regions.
Inputs: domain (required), months, response_format. Returns: result
watch_domainsBRead-onlyIdempotent
A radar over 2-8 competitors: new hostnames in the window and each one's top launch signals.
Inputs: domains (required), days, response_format. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct aspect: ranked signals, raw hostname evidence, temporal aggregation, multi-domain radar, and single-hostname history. However, launch_signals and new_subdomains overlap in output (product-like names with environment words), differing mainly in ranking vs raw framing, so minor confusion is possible.
All tools use lower_snake_case with two-word names (launch_signals, new_subdomains, subdomain_timeline, hostname_history); watch_domains is the only verb-led name but still follows the same delimiter style. No mixing of conventions.
5 tools is well-scoped for a focused launch-detection service. Each tool covers a distinct analytical angle without redundancy or thinness.
Covers signal detection, raw evidence, timeline, competitor watch, and hostname history—core workflows for the domain. Minor gaps: no tool to list all current subdomains for a domain (only new ones in a window) or to search product names across multiple domains, but these are workable.
Maintenance
Related MCP Connectors
Passive subdomain enumeration from certificate transparency (certspotter, crt.sh) with DNS checks.
Query crt.sh SSL/TLS Certificate Transparency logs for subdomain discovery and certificate audits.
Certificate Transparency search: subdomains, certificate history and hostname keyword search.
Passive OSINT and security recon: DNS, TLS, email posture, IP reputation, CVE/KEV, CT logs.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables SSL/TLS certificate search and analysis using crt.sh data, supporting domain certificate discovery, subdomain enumeration, and security auditing through Cloudflare Workers deployment.-
- AlicenseAqualityBmaintenanceEnables named-entity attribution from Certificate Transparency logs (OV/EV only) for mapping legal-entity digital footprints and domain discovery via LLM-driven workflows.734 npmMIT
- AlicenseNot gradedqualityBmaintenancePassive external attack-surface mapping server that discovers subdomains, DNS records, TLS posture, HTTP headers, and registration data via public sources like CT logs, Shodan, and RDAP/WHOIS, enabling security reconnaissance without active scanning.221 npm2Apache 2.0
- AlicenseAqualityCmaintenanceEnables LLMs to query Certificate Transparency logs via CertIndex API, allowing searches for TLS certificates, subdomains, and certificate metadata.649 PyPIMIT