Product Discovery Prover MCP. Validate assumptions. Prove product viability before writing code.

You got product ideas that sound great in a meeting room but fall apart when they meet reality. Don't waste time and money building something nobody needs. The validate_product_discovery tool forces you to prove your concept is real—it runs a structured review on any hypothesis, demanding hard proof across five critical areas before an engineer writes a single line of code.

This isn't a suggestion list; it’s a gate that requires documented evidence. You gotta show the problem exists at scale and that people are ready to pay for the fix.

To prove problem existence at scale, you can’t just say 'it's a pain point.' The tool demands specific metrics showing genuine market need. It makes you cite actual data points—things like sustained high search volume on problem-related keywords or documented trends in existing support ticket logs that track the severity of the issue.

You gotta show quantifiable proof that the struggle is widespread and persistent.

The server forces definition of customers by observable behavior, not vague demographics. Forget saying 'small businesses.' Instead, you'll define segments based on actions: maybe it’s 'solo accountants who are currently using three different spreadsheets to track payroll,' or 'freelance designers whose workflow consistently breaks when they move files between programs.' The system requires mapping these behavioral friction points—the abandoned alternatives and the specific steps in a user's current process that cause headaches.

You must map out competitor weaknesses by documenting hands-on testing results. You don’t get to just read their website; you have to test their actual products against real tasks for at least one week. The tool forces you to identify clear, exploitable gaps—where they fail or where the user hits a wall—and calculate the switching cost.

If your solution isn't dramatically easier than what they offer right now, you haven’t proven anything.

The server separates genuine intent from polite compliments when verifying financial commitment. It demands evidence of concrete spending readiness. You need proof like pre-payments or signed Letters of Intent (LOIs) that show someone is willing to put money down before the product exists. If people are just saying, 'I love this idea,' you fail this check.

You gotta prove actual capital commitment.

Finally, it constrains your efforts by scoping rapid experiments. It forces you to define a core hypothesis and an experiment so minimal that you can test it in four weeks or less. This isn’t about building the whole product; it's defining the single riskiest assumption and proving it wrong—or right—as fast as possible.

If your proposed scope drags out past one month, it ain't an MVP, and you don't get to test it here.

This process strips away assumptions that founders build their careers on. It prevents solution-seeking problems by demanding proof of pain and demand before the first line of code is written. You walk into development with hard data backing up every claim.