Skip to main content
Glama

🚀 prelaunch-mcp

Smarter pre-build reality check for AI agents.

Stop building what already exists. prelaunch-mcp scans 6 sources with LLM-powered intent parsing to tell you if your idea has competition, if there's real demand, and where the gaps are.

✨ What Makes This Different

Feature

Other validation tools

prelaunch-mcp

Intent understanding

Dictionary keyword stripping

🧠 LLM-powered intent parsing

Search queries

Generic keyword variants

Targeted competitor-finding queries

Sources

3-5 dev-only sources

6 (GitHub, HN, npm, PyPI, Google/DDG, Reddit)

Scoring

Simple bucket math

Relevance-weighted with intelligent caps

Demand signals

❌ None

✅ Reddit pain signal detection

Insights

Static templates

Context-aware dynamic insights

Output

Single score

competition_score + demand_score + gap analysis

Related MCP server: idea-reality-mcp

📦 Installation

For Claude Code / Cursor / Windsurf

# Add to your MCP config
claude mcp add prelaunch -- uvx prelaunch-mcp

For other MCP clients

Add to your MCP config (e.g., .claude.json, mcp.json):

{
  "mcpServers": {
    "prelaunch": {
      "command": "uvx",
      "args": ["prelaunch-mcp"],
      "env": {
        "ANTHROPIC_API_KEY": "your-key-here",
        "GITHUB_TOKEN": "your-token-here"
      }
    }
  }
}

Run directly

uvx prelaunch-mcp

🔑 Environment Variables

All API keys are user-provided. We never store or transmit your keys.

Variable

Required

Purpose

ANTHROPIC_API_KEY

Recommended

LLM intent parsing (Claude Haiku — ~$0.001/check)

OPENAI_API_KEY

Alternative

LLM parsing via OpenAI or compatible API

OPENAI_BASE_URL

Optional

Custom endpoint (Ollama, LM Studio, etc.)

GITHUB_TOKEN

Optional

Higher GitHub API rate limits

GOOGLE_CSE_KEY

Optional

Google Custom Search (falls back to DuckDuckGo)

GOOGLE_CSE_ID

Optional

Google Custom Search Engine ID

Without any API keys, the tool still works using fallback keyword extraction and all free sources (GitHub, HN, PyPI, npm, DuckDuckGo, Reddit).

🎯 Usage

Once installed, your AI agent can call it naturally:

"Check if anyone has built an AI agent security scanner"
"Is there competition for a Kubernetes cost optimization dashboard?"
"Run a pre-launch check on: open-source compliance tool for Indian banks"

Depth Modes

Mode

Speed

Sources

LLM

quick

⚡ Fast

GitHub + HN

No

standard

🔄 Balanced

All 6 sources

Yes (if key available)

deep

🔍 Thorough

All 6 + extra queries

Yes (if key available)

📊 Example Output

{
  "competition_score": 42,
  "demand_score": 60,
  "competition_level": "high",
  "intent": {
    "category": "security",
    "product_type": "CLI tool",
    "target_audience": "AI engineers",
    "target_technology": "LangChain, CrewAI",
    "analogy": "npm audit but for AI agents",
    "core_problem": "No automated security scanning for AI agent deployments"
  },
  "top_similars": [...],
  "pain_signals": [
    {
      "title": "Anyone built security tooling for LangChain agents?",
      "url": "https://reddit.com/...",
      "subreddit": "LangChain",
      "score": 47
    }
  ],
  "insights": [
    "🟡 Moderate competition — the space exists but isn't saturated.",
    "🔥 Strong demand signal: 3 Reddit posts expressing unmet need.",
    "✅ Promising: competition validates market AND demand signals confirm unmet needs.",
    "🧭 Analogy: \"npm audit but for AI agents\" — validate dynamics apply to security."
  ]
}

🔧 Development

# Clone
git clone https://github.com/Heman10x-NGU/prelaunch-mcp.git
cd prelaunch-mcp

# Install deps
uv sync --dev

# Run tests
uv run pytest tests/ -v

# Run server locally
uv run prelaunch-mcp

Architecture

Input: "AI agent security scanner like npm audit for CrewAI"
    │
    ├── Stage 1: LLM Intent Parse (or fallback keywords)
    │   → category: "security" | type: "CLI tool" | queries: [...]
    │
    ├── Stage 2: Multi-Source Scan (parallel)
    │   → GitHub, HN, PyPI, npm, Google/DDG, Reddit
    │
    └── Stage 3: Scoring & Analysis
        → competition_score + demand_score + gap insights

License

MIT

Available Tools

1 tool
prelaunch_checkA

Check if a product idea already exists before building it.

A smarter pre-build reality check that uses LLM-powered intent parsing (when API key is available) and multi-source scanning.

Uses:

  • Discuss new project ideas

  • Check competition

  • Validate market demand

  • Find if something has been built before

Environment variables (user provides their own):

  • ANTHROPIC_API_KEY or OPENAI_API_KEY — for LLM-powered intent parsing (optional but recommended)

  • GITHUB_TOKEN — for higher GitHub API rate limits (optional)

  • GOOGLE_CSE_KEY + GOOGLE_CSE_ID — for Google search (optional, DuckDuckGo fallback)

Args: idea_text: Natural-language description of the idea. depth: - "quick": GitHub + HN only, no LLM (fastest) - "standard": All sources in parallel + LLM intent parsing (recommended) - "deep": Everything in standard + extra query variants (most thorough)

Returns: Reality check report with competition score, demand score, evidence, similar projects, pain signals, and actionable insights.

Inputs: idea_text (required), depth. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool available, there is no possibility of selecting the wrong tool or confusing it with another. The purpose of prelaunch_check is clearly defined and unambiguous.

    Naming Consistency5/5

    The single tool name 'prelaunch_check' follows a clean verb_noun pattern that is consistent with common MCP naming conventions. No inconsistent naming schemes exist since there is only one tool.

    Tool Count3/5

    A single tool feels thin for a server, but it is acceptable for a narrowly focused prelaunch validation utility. The tool bundles several internal capabilities (LLM parsing, source scanning) into one entry point, making the count borderline but not unreasonable.

    Completeness4/5

    The tool covers the server's core purpose of checking whether a product idea already exists, with multiple depth modes and evidence gathering. However, it lacks secondary operations like saving results, comparing multiple ideas, or managing check history, leaving minor gaps.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Pre-build reality check for AI coding agents. Scans GitHub, Hacker News, npm, PyPI & Product Hunt in parallel — returns a 0-100 reality signal with real competitor data.
      1
      75 PyPI
      832
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Pre-build reality check for AI coding agents — searches 5 real databases (GitHub, Hacker News, npm, PyPI, Product Hunt) to check whether an idea already exists before you build it.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides VC-grade startup intelligence, allowing founders to validate ideas and VCs to screen deals using tools like scoring, investor matching, and financial analysis.
      9 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Automates competitive research for startup ideas by executing a 7-step pipeline including idea understanding, competitor discovery, profile extraction, feature comparison, market gap analysis, innovation scoring, and report generation.
      8
      MIT