@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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。