@trigvale/mcp
Validates startup ideas with a deterministic scorecard, evidence brief, and verdict before code is written, integrating with MCP-aware build agents to avoid building dead-on-arrival products.
README
@trigvale/mcp
MCP server for Trigvale — validate startup ideas before your build agent scaffolds code.
This is the official Model Context Protocol server for Trigvale. It exposes one tool, validate_idea, to MCP-aware build agents (Cursor, Claude Code, Codex, Claude Desktop). The intended UX is straightforward: your agent calls validate_idea before it writes a single line of scaffolding. A green or amber verdict greenlights coding; a red verdict surfaces the assumption you should test first.
What validate_idea returns
- 10-dimension scorecard — Venture Readiness Score (VRS, 0–100), computed deterministically in code from the model's per-dimension scores against published anchors. The model never picks the VRS itself.
- Evidence brief — every item tagged by
sourceKind∈ {observed,inferred,missing,ai,user-claim} so you know what's grounded vs assumed. - Verdict —
kill,pivot,test, orbuild. Build is rare by construction. - Founder-fit calibration — per-dimension deltas applied from the user's declared skill graph (declared inputs only — never extrapolates from past failures).
- 1–3 archetype assignments — clusters the idea into known patterns (e.g. "vertical-ai-saas", "agentic-workflow") with structural cautions for the cluster.
- Live evidence — real-time pull from Reddit, GitHub, Hacker News, Stack Overflow, and dev.to for the idea's dominant archetype, refreshed every 6 hours.
Full output schema and methodology: https://trigvale.com/methodology
Install
npx -y @trigvale/mcp
You'll need a Trigvale agent token (Integrate plan, $99/mo). Get one at https://trigvale.com/settings.
Configuration
Drop this into your MCP client's config (mcpServers block):
Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"trigvale": {
"command": "npx",
"args": ["-y", "@trigvale/mcp"],
"env": {
"TRIGVALE_AGENT_TOKEN": "tvk_xxx"
}
}
}
}
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS)
Same shape — replace tvk_xxx with your token from /settings.
Claude Code
Add the snippet to .mcp.json at the repo root, or use claude mcp add to register it interactively.
Self-hosted / dev environments
Override the API base via env:
TRIGVALE_API_BASE_URL=https://api-dev.trigvale.com npx -y @trigvale/mcp
Default base is https://api.trigvale.com (production).
Example usage in an agent prompt
"Before you scaffold this project, call
validate_ideawith the user's pitch. If the verdict iskillorpivot, surface the weakest assumption and ask the user whether to proceed anyway. Iftest, suggest the validation sprint Trigvale recommends before any code."
Why a separate validation step?
Building has gotten cheap. The bottleneck is no longer execution — it's deciding what to execute. Most ideas should be killed, pivoted, or tested before code is written. validate_idea makes that decision an explicit, repeatable step in your agent flow, with a deterministic verdict and source-tagged evidence you can show the user.
Pricing & plans
| Plan | Monthly | Includes |
|---|---|---|
| Free | $0 | 1 verdict / month, lite preview |
| Starter | $12 | 10 verdicts / month, full brief |
| Validate | $39 | Live evidence pipeline + sharpening + sprint generator |
| Integrate | $99 | Everything above + agent tokens for this MCP server |
The agent token required by this MCP is gated to the Integrate plan. Per-call entitlement is re-checked server-side on every /agent/v1/evaluate call — downgrades take effect immediately.
Full pricing: https://trigvale.com/pricing
Source
This is a read-only mirror of the MCP server source from Trigvale's private monorepo (the rest of which contains the proprietary rubric, infrastructure, and billing logic). Releases are cut on the private side and synced here. PRs are welcome — please open issues at https://trigvale.com/contact instead of GitHub Issues so we route them through the support workflow.
License
MIT — sydacos GmbH, 2026.
Links
- Homepage: https://trigvale.com
- Integration docs: https://trigvale.com/integrations
- Methodology: https://trigvale.com/methodology
- Sample brief: https://trigvale.com/sample
- Contact: https://trigvale.com/contact
- npm: https://www.npmjs.com/package/@trigvale/mcp
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.