Index / MCP servers / Demand Discovery AI

Demand Discovery AI MCP server

Demand Discovery AI is an MCP server with 10 tools an agent can call, among them ask_demand_discovery, compare_validation_approaches, explain_demand_signals. It answers at https://mcp.demanddiscovery.ai/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Status
Answering
Tools
10
Official
yes, served from demanddiscovery.ai
Reliability
10 of 10 checks
Response time
293 ms
Transport
streamable HTTP
Last checked
17 October 2026

Validate startup ideas with real people asking for them, each quote linked to its source.

Description as the publisher wrote it.

The 10 tools Demand Discovery AI offers

ToolWhat it does
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 workarounds
Inputs: question
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, asking
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 user
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 do
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 s
Inputs: orderId
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 a
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 "h
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 an
Inputs: reportId, email, alTriggerToken
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 text
Inputs: name, problem, solution, target_market, current_workaround, email
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 wi
Inputs: reportId, email, name, problem, solution, target_market

Add Demand Discovery AI to your AI client

Every block below points at https://mcp.demanddiscovery.ai/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http demand-discovery-ai https://mcp.demanddiscovery.ai/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "demand-discovery-ai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.demanddiscovery.ai/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "demand-discovery-ai": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "demand-discovery-ai": {
      "type": "http",
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "demand-discovery-ai": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "demand-discovery-ai": {
      "serverUrl": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "demand-discovery-ai": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Demand Discovery AI
version: 0.0.1
schema: v1
mcpServers:
  - name: Demand Discovery AI
    type: streamable-http
    url: https://mcp.demanddiscovery.ai/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "demand-discovery-ai": {
      "httpUrl": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "demand-discovery-ai": {
      "type": "http",
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "demand-discovery-ai": {
      "url": "https://mcp.demanddiscovery.ai/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.demanddiscovery.ai%2Fapi%2Fmcp&type=streamable_http&id=demand-discovery-ai&name=Demand%20Discovery%20AI

Is Demand Discovery AI up right now?

It answered our last check on 17 October 2026 in 293 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Demand Discovery AI

Questions about Demand Discovery AI

Is there an official Demand Discovery AI MCP server?

Yes. It is published by demanddiscovery.ai and served from mcp.demanddiscovery.ai, the vendor's own domain: https://mcp.demanddiscovery.ai/api/mcp.

How many tools does Demand Discovery AI have?

10, as returned by the server's own tools/list on 7 September 2026: ask_demand_discovery, compare_validation_approaches, explain_demand_signals, get_data_source_categories, get_demand_report_status, get_product_details, get_validation_framework, start_agentic_launch, and 2 more.

Is Demand Discovery AI down?

It answered our last check on 17 October 2026 in 293 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add Demand Discovery AI to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.demanddiscovery.ai/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Demand Discovery AI need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: ai.demanddiscovery. Endpoint host: mcp.demanddiscovery.ai. ARD identifier: urn:air:ai.demanddiscovery:mcp:mcp. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.