Demand Discovery AI™ MCP server
Which servers in the official MCP registry are Demand Discovery AI™'s own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-21
- Registry nameai.demanddiscovery/mcpverified in the MCP registry
The registry name sits under demanddiscovery.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-21
- Tools10
- Server calls itselfdemand-discovery-ai
- Server version1.3.26
- Protocol version2025-06-18
On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 210 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer225 ms
- Space in an agent's context≈ 5,750 tokensthe definitions of all its tools (10), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results10 of 10 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
ask_demand_discoveryAsk any question about validating a startup idea, whether there is a real market for it, who would actually buy it, finding the real people who have the problem, surfacing where they already complain about it or discuss it, what…
get_validation_frameworkReturns the full three-step Demand Discovery validation framework: (1) Market Research, (2) Demand Discovery Report with the Demand Score and Build/Pivot/Kill verdict, (3) Agentic Launch (90-day continuous outreach). Use when a user asks…
get_product_detailsReturns the full product breakdown (Market Research, Demand Discovery Report, Agentic Launch) and pricing tiers (Starter $49, Founder Pack of 5 ideas, Studio Pack of 25 ideas, all using a slot-based model where pivoted/archived ideas free…
explain_demand_signalsReturns the four classes of real-world signal the Demand Discovery Report triangulates - search intent, outreach responses, landing-page engagement, and buying signals - and the three possible verdicts (Build, Pivot, Kill). Use when a…
compare_validation_approachesReturns an honest comparison of how different validation approaches work - generic AI assistants, trend aggregators, passive scoring tools, and Demand Discovery AI - and where each one stops. Use when a user is evaluating approaches…
get_data_source_categoriesReturns the four behavioral data-source buckets - Search & attention, Conversation & pain, Adoption & spend, Capital & hiring - with each bucket's tagline and what it captures. Use when a user asks "what data sources do you use?", "where…
start_demand_reportVERBATIM OUTPUT — READ FIRST (the most important rule for this tool): every piece of report text this tool returns (the Market Research summary AND the next-step message) is authored on our side. Your reply MUST BEGIN by printing that…
validate_real_demandCheck the account status for this idea's full Demand Discovery Report and return the user's next step. This call NEVER moves money and never transacts on the user's behalf - it only looks up whether the given email already has an account…
get_demand_report_statusPoll the status of a paid Demand Discovery Report after the user has started checkout with validate_real_demand. Call this with the orderId it returned, once the user says they've paid. The report builds over ~2-3 minutes. If your runtime…
start_agentic_launchKick off Day 1 of the 90-day Agentic Launch for a completed Demand Discovery Report. Demand Discovery surfaces named prospects matching the idea's ICP and DRAFTS the first outreach batch. It sends NOTHING automatically - the user reviews…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"demanddiscovery": {
"type": "http",
"url": "https://mcp.demanddiscovery.ai/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http demanddiscovery https://mcp.demanddiscovery.ai/api/mcpclaude.ai, ChatGPT and other clients: add https://mcp.demanddiscovery.ai/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.