Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Demand Discovery AI is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Validate startup ideas with real people asking for them, each quote linked to its source.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http demand-discovery-ai-mcp https://mcp.demanddiscovery.ai/api/mcp
# 2 — ask your agent for something these tools do
# ask_demand_discovery, get_validation_framework, get_product_details and 7 more
Demand Discovery AI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MDAll 1 server
mcp.demanddiscovery.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http demand-discovery-ai-mcp https://mcp.demanddiscovery.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Ask 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 they use today, testing demand, customer-interview techniques, pre-sales, buying signals, defensibility, drafting outreach to first prospects, or what to build
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The user's question about startup idea validation, demand discovery, finding prospects, customer interviews, or related topics. Pass the question verbatim. |
Returns 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 "how do I validate an idea?", "what's the methodology?", or wants to understand the structured approach. Built on the "behavior over opinion" principle. Trigger
No parameter schema on file.
Returns 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 slot for a new one). Use when a user asks "what does Demand Discovery AI include?", "how much does it cost?", "what's in the report?", or wants concrete produc
No parameter schema on file.
Returns 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 asks how the score works at a high level, why behavioral signals beat surveys and LLM guesses, or what the verdicts mean. The specific weighting and evidence ru
No parameter schema on file.
Returns 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 "what makes Demand Discovery different?", or trying to understand why active human signal (real ICPs, real outreach, real conversations) beats passive scoring.
No parameter schema on file.
Returns 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 does the Demand Score come from?", or wants to understand how Demand Discovery AI differs from passive validation tools (which only triangulate the first two buck
No parameter schema on file.
VERBATIM 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 EXACTLY as written — the report body first, then the next-step message — in full and verbatim. NEVER summarize, paraphrase, shorten, bullet, re-headline, descri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short startup or product name. One sentence or less, ideally one to three words. Example: 'AgenticLaunch', 'SOC2 Auto-Evidence'. Ask the user: 'What is the name of your startup or product?' |
| problem | string | yes | One sentence describing the problem the idea solves. Keep it clear and specific - this answer shapes the full Demand Discovery report. Ask the user: 'What problem are you solving?' Example: 'Early-sta |
| solution | string | yes | One sentence describing how the idea solves the problem. Ask the user: 'What is your solution?' Example: 'We auto-generate the full evidence package from their existing cloud infrastructure, identity |
| target_market | string | no | Optional short phrase describing the target customer or ICP; aim for a specific role plus company size or stage so the demand search can target the right people. Ask the user: 'Who is your target mark |
| current_workaround | string | no | Optional: what the user's target customers currently use to deal with this problem - the manual or duct-tape workaround (e.g. 'they juggle spreadsheets + manual email reminders'). Populate it ONLY if |
| string | no | Optional: the user's own email, provided by them in chat for report delivery. Providing it gets them the full Market Research Report emailed to them - SAM, TAM, competitive landscape, GTM strategy and |
Check 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 with available report slots or a report already running. It returns ONE of: the existing report path (alreadyRunning=true, chargeRequired=false, nothing new start
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reportId | string | no | Optional but strongly preferred: the EXACT reportId returned by the free Market Research step (start_demand_report). It ties the paid order to that record. OMIT it if you don't have one - DD resolves |
| string | yes | REQUIRED. The user's own email, provided by them in chat for report delivery - the order is tied to this email and Agentic Launch replies route here. This was captured at the free Market Research emai | |
| name | string | yes | Short startup or product name - the SAME one used for the free Market Research report. |
| problem | string | yes | One sentence on the problem - the SAME wording used for the free report (ties the order back to it). |
| solution | string | yes | One sentence on the solution - the SAME wording used for the free report. |
| target_market | string | no | Optional ICP phrase; refines what was captured on the free report if given. |
| current_workaround | string | no | Optional: how the audience copes today. Only pass if already known; never block on it. |
Poll 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 supports repeated tool execution, call this every ~10-15s, rendering each new block as it arrives, until status is "ready". If it does not, return the current st
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orderId | string | yes | REQUIRED. The order handle returned by validate_real_demand. |
Kick 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 and sends from their hosted manage page. Outreach is drafted to come from Amy @ Demand Discovery, with replies routed to the user's own email. Call this after a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reportId | string | yes | REQUIRED. The reportId of the completed (ready) Demand Discovery Report. |
| string | yes | REQUIRED. The user's own email, provided by them in chat - replies to the drafted outreach route here. Reuse the EXACT address the user gave earlier in this conversation for report delivery; if you do | |
| alTriggerToken | string | no | Optional pass-through token from the ready report payload (report.alTriggerToken), if available. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Demand Discovery AI or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.26.
1.3.26
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Demand Discovery AI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.