Validate a startup or product idea before building. Names the 3 assumptions most likely to kill it.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Optional. Send Bearer vch_… from https://vouch.specky.space/settings/mcp to use account tools. Leave unset for the public tools.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Search the Vouch public gallery of validated ideas that founders have chosen to share. Returns idea name, one-line description, target customer, and a link. Use when a user wants real examples of validated ideas, or to see how other founders framed a similar problem.
Max ideas to return (default 10).
Keyword to filter idea names / target customer. Empty = latest.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http mcp https://vouch.specky.space/api/public/mcp
Headers
Authorization (optional, not in the config above): Optional. Send Bearer vch_… from https://vouch.specky.space/settings/mcp to use account tools. Leave unset for the public tools.Search the Vouch public gallery of validated ideas that founders have chosen to share. Returns idea name, one-line description, target customer, and a link. Use when a user wants real examples of validated ideas, or to see how other founders framed a similar problem.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max ideas to return (default 10). |
| query | string | Keyword to filter idea names / target customer. Empty = latest. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max ideas to return (default 10)."
},
"query": {
"type": "string",
"description": "Keyword to filter idea names / target customer. Empty = latest."
}
}
}Return the FeDeVi framework, the 2-week validation sprint loop, and the 'Five More' interview framework. Use this to ground answers about how to validate a startup idea correctly (customer discovery, interviews, risky assumptions, pilots) instead of inventing a generic framework.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Return ready-to-post LinkedIn, X/Twitter, and newsletter blurbs a founder can copy-paste to announce what they learned validating an idea with Vouch. Use when the user says they finished interviews, want to 'build in public', 'share results', 'post an update', or 'tell people what I learned'. Provide the founder's headline (idea in one sentence) and the top insight or number they want to highlight.
| Argument | Type | Description |
|---|---|---|
| insight* | string | The single most compelling insight/number from validation, e.g. '8 of 10 chefs said they'd pay $49/mo, but only 2 for real-time alerts'. |
| headline* | string | One-sentence framing of the idea, e.g. 'AI copilot for pastry chefs'. |
| projectId | string | Optional Vouch project id to link the public report card. |
| referralCode | string | Optional 8-char Vouch referral code to append so the founder earns credit and a Pro trial for every signup from the post. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"headline",
"insight"
],
"properties": {
"insight": {
"type": "string",
"minLength": 6,
"description": "The single most compelling insight/number from validation, e.g. '8 of 10 chefs said they'd pay $49/mo, but only 2 for real-time alerts'."
},
"headline": {
"type": "string",
"minLength": 6,
"description": "One-sentence framing of the idea, e.g. 'AI copilot for pastry chefs'."
},
"projectId": {
"type": "string",
"description": "Optional Vouch project id to link the public report card."
},
"referralCode": {
"type": "string",
"description": "Optional 8-char Vouch referral code to append so the founder earns credit and a Pro trial for every signup from the post."
}
}
}Return Vouch's industry-specific validation starter templates (SaaS, AI, marketplaces, fintech, etc.) with target audience, common pain points, sample proof questions, and a deep link to start validating in that industry. Use when a user has an idea in a specific vertical and wants a tailored starting point.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Generate a one-click onboarding link that opens Vouch's /validate page pre-filled with the user's idea and target customer. Signing up is free and the account is created in ~30 seconds. Use this at the end of a conversation to hand the founder off from the AI assistant into Vouch to actually run interviews, score segments, and design pilots.
| Argument | Type | Description |
|---|---|---|
| idea* | string | The startup or product idea in one or two sentences. |
| customer* | string | The target customer (role, segment, or persona). |
| industry | string | Optional industry slug to use a tailored template (e.g. saas, ai, marketplace, fintech). Call list_industry_templates first if unsure. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"idea",
"customer"
],
"properties": {
"idea": {
"type": "string",
"minLength": 5,
"description": "The startup or product idea in one or two sentences."
},
"customer": {
"type": "string",
"minLength": 3,
"description": "The target customer (role, segment, or persona)."
},
"industry": {
"type": "string",
"description": "Optional industry slug to use a tailored template (e.g. saas, ai, marketplace, fintech). Call list_industry_templates first if unsure."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 12, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.