# Competitive Intelligence Prover MCP > Competitive Intelligence Prover forces AI analysis to stick to verifiable facts. It validates competitor claims by requiring sources like G2 IDs, pricing pages, and GitHub issues. Stop building strategies on guesses; generate plans with measurable weaknesses, clear timelines, and undeniable evidence. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** competitive-intelligence, competitor-analysis, strategy, anti-hallucination, market-research, business-strategy, agentic-pipeline ## Description Standard AI agents are great at sounding confident, but they're terrible at staying factual when talking about competitors. They tend to hallucinate market share numbers or list vague problems like 'poor UX' without backing them up. This MCP solves that. It doesn't just give you a strategy; it demands proof for every claim made about your rivals. You feed in the raw analysis, and this tool forces six specific checks: Does every data point cite its source? Are the weaknesses measurable (e.g., '14-step onboarding')? Is the proposed attack plan actually feasible given your team's size and budget? By integrating it with Vinkius, you connect to a specialized intelligence pipeline that transforms guesswork into actionable, evidence-backed plans. You walk away with strategies tied to real deadlines and quantifiable success metrics. ## Tools ### validate_competitive_intel Validates competitive analysis by checking if every claim cites a verifiable source, if weaknesses are measurable, and if the proposed strategy is feasible with defined resources. ## Prompt Examples **Prompt:** ``` Competitor X has approximately $50M in revenue and about 30% market share. They have poor UX and limited features. We should build a better product and outspend them on marketing to win the market. ``` **Response:** ``` Verdict: EVIDENCE_MISSING. Triple failure. (1) '$50M revenue' and '30% market share' — WHERE? No SEC filing, no Crunchbase link, no source. Likely fabricated. (2) 'Poor UX' and 'limited features' — vague opinions, not intelligence. Test their product and document specifics. (3) 'Build better and outspend' — generic playbook, no WHO/WHEN/COST. Rewrite with verifiable sources, measured weaknesses, and execution plan. ``` **Prompt:** ``` Competitor: Acme CI/CD. Evidence: pricing page shows $49/user/month (verified 2024-01-20). G2 reviews #14523, #14601, #14789: 'slow builds', 'no ARM support', 'expensive for small teams'. Our testing (2024-01-18): build time 12min vs our 3min for identical repo. GitHub issues: 234 open about ARM (#4521, #4589). Job postings: 0 DevRel, 3 enterprise sales. Weakness: no ARM (verified), 4x slower builds (tested), no free tier (pricing). Attack: 'Migrate from Acme' page targeting 'acme... ``` **Response:** ``` Verdict: STRATEGY_PROVEN. Evidence-based (pricing verified, G2 with IDs, hands-on testing with dates, GitHub issues cited). Weaknesses quantified (no ARM — 234 issues, 4x slower — tested, no free tier — pricing). Strategy feasible (1 engineer, 5 days, $0). Self-aware (SOC2/SAML gap). Differentiated ('acme alternative ARM' keyword). Metrics with kill criterion. Execute. ``` **Prompt:** ``` Competitor Y's onboarding has issues (we heard from users). They're expensive. We should target their unhappy customers with a better price and better experience. ``` **Response:** ``` Verdict: VAGUE_WEAKNESS. Three gaps: (1) 'Has issues' and 'expensive' — WHAT issues? HOW expensive vs you? No G2 reviews, no testing, no pricing comparison. (2) 'We heard from users' is not evidence. Cite specific Reddit threads, G2 reviews with IDs, or your own testing with dates. (3) 'Better price and better experience' is a generic playbook — this applies to any competitor. Define: WHAT specific onboarding problem? HOW MANY steps vs yours? WHAT exact price comparison? HOW do yo... ``` ## Capabilities ### Verify Competitor Claims Forces every competitor claim—from revenue figures to feature lists—to cite a specific, verifiable source like SEC filings or G2 review IDs. ### Quantify Weaknesses Turns vague opinions into measurable intelligence by requiring observable data points (e.g., 'build time 12min' vs. your test result). ### Model Feasible Attack Plans Requires defining the WHO, WHEN, and COST for any proposed strategy to ensure it’s actually executable with current resources. ### Conduct Self-Aware Analysis Forces the analysis to acknowledge your company's own vulnerabilities alongside the competitor's strengths. ### Set Success Metrics Adds measurable kill criteria and leading/lagging indicators with hard deadlines, so you know exactly when a plan succeeds or fails. ## Use Cases ### Launching into a new market segment A PM needs to challenge the market leader. They input data that includes 'Competitor Y has poor UX.' The MCP immediately rejects this, forcing them instead to document specific findings: '14-step onboarding' and link the G2 review ID confirming setup time. ### Pitching a new product feature A team drafts a strategy based on competitor gaps. They use the MCP, which flags that the plan is too ambitious (e.g., 'build an enterprise platform') and forces them to redefine it for their current 3-engineer resource pool. ### Responding to investor due diligence The founder has a pile of market research but needs verifiable facts. Running the data through this MCP ensures that every claim about market size or revenue is tied to an official filing, making the pitch bulletproof. ## Benefits - Stop relying on vague statements. The tool forces you to prove every market claim, citing things like specific G2 review IDs or pricing pages instead of just saying 'poor UX'. - You get concrete attack plans. Instead of a general recommendation like 'improve marketing,' the MCP demands WHO will execute it, what the timeline is, and how much it costs. - It forces self-awareness. The analysis doesn't just point out competitor weaknesses; it also acknowledges your company's own gaps, which is crucial for realistic planning. - You eliminate hallucinated data. By mandating verifiable sources (SEC filings, Crunchbase), you guarantee that the intelligence passed to your team is accurate and legally defensible. - The output includes kill criteria. This means every strategy comes with a measurable success metric and a deadline—you know exactly when to pivot or declare victory. ## How It Works The bottom line is you get an anti-hallucination filter that turns confident guesswork into actionable, fact-grounded intelligence. 1. Submit your raw competitive analysis (e.g., 'Competitor X has poor UX' and 'They make $50M'). 2. The MCP runs the data through its six-axis validation process, checking for sources, feasibility, and metrics. 3. You receive a verdict: either STRATEGY_PROVEN with concrete next steps, or EVIDENCE_MISSING detailing exactly which claims need verifiable support. ## Frequently Asked Questions **How does the Competitive Intelligence Prover MCP handle general market trends?** It treats them like any other claim. It won't accept vague statements about 'market growth'; it will demand a source, like an industry report or government filing. **Do I need to manually input all the data for validate_competitive_intel?** While you provide the initial analysis, the MCP guides your inputs by demanding specific types of evidence (e.g., a review ID) and flags anything lacking that proof. **Can I use this MCP to compare my own internal metrics against a competitor?** Yes, you provide your test results (like 'our 3-minute build time'), and the tool compares it against the cited competitor data, quantifying the gap. **Is this better than just asking my AI client for analysis?** Absolutely. Your agent generates text; this MCP runs a rigid validation process that forces external proof, turning persuasive writing into undeniable evidence. **How does the `validate_competitive_intel` command handle varied sources like G2 reviews and GitHub issues?** It cross-references multiple verifiable data types simultaneously. The tool doesn't rely on just one source; it synthesizes information from pricing pages, user review IDs, job postings, and technical issue trackers to build a comprehensive evidence profile. **Is the sensitive competitor data processed by `validate_competitive_intel` kept secure?** Yes, all competitive intelligence is processed within Vinkius's encrypted environment. We treat this information as highly confidential; your inputs and outputs are managed using industry-standard security protocols. **Are there rate limits when I run `validate_competitive_intel` for multiple competitors?** Vinkius manages throttling to maintain stable performance across all users. For high-volume analysis, check your account dashboard; exceeding the allocated limit will return a specific 429 status code. **What should I do if `validate_competitive_intel` fails or returns an ambiguous error?** Always check the full API output for a detailed error code and message. If the core logic fails, review your prompt to ensure all required components, like WHO, WHEN, and COST, are explicitly defined. **How does it prevent hallucination?** The engine detects 16+ hallucination markers: 'approximately', 'reportedly', 'sources suggest', 'believed to', 'likely has', 'probably', etc. Any hedging language triggers rejection. Every claim must cite a verifiable source: their website, G2/Capterra reviews with IDs, Crunchbase, SEC filings, Reddit threads, or your own hands-on testing. If you can't cite the source, you must delete the claim. **What sources are acceptable?** Seven categories: (1) Their website — pricing pages, feature docs, changelogs. (2) Review platforms — G2, Capterra, TrustRadius with specific review IDs. (3) Public financials — Crunchbase funding, SEC filings, press releases. (4) User complaints — Reddit threads, GitHub issues, support forums. (5) Job postings — reveals tech stack, team gaps, growth areas. (6) Your own testing — 'We signed up and tested on [date].' (7) App Store/Play Store reviews. Minimum 3 independent sources to triangulate. **Why does it require self-assessment?** Because competitors also analyze YOU. An analysis that only shows 'they're bad, we're good' is self-deception that leads to strategic blindness. The tool forces you to acknowledge: (1) Where are YOU vulnerable? (2) What do THEY do better? (3) How would THEY attack your weak points? (4) What blind spots exist? The best competitive strategies are brutally honest about both sides.