Proofstack MCP server
{
"mcpServers": {
"proofstack": {
"type": "http",
"url": "https://proof-stack-lake.vercel.app/mcp"
}
}
}{
"mcpServers": {
"proofstack": {
"type": "http",
"url": "https://proof-stack-lake.vercel.app/mcp"
}
}
}{
"mcpServers": {
"proofstack": {
"type": "http",
"url": "https://proof-stack-lake.vercel.app/mcp"
}
}
}{
"servers": {
"proofstack": {
"type": "http",
"url": "https://proof-stack-lake.vercel.app/mcp"
}
}
}{
"mcpServers": {
"proofstack": {
"type": "http",
"url": "https://proof-stack-lake.vercel.app/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
ProofStack exposes a library of 43 audited indie product business cases with sourced pricing, revenue, and acquisition data. Each figure is linked to its published source, allowing AI assistants to cite evidence. Developers use it to research pricing strategies, revenue benchmarks, and business model patterns for indie products.
- Query pricing benchmarks across categories to understand median first paid tiers, free-tier prevalence, and paywall patterns for indie products
- Search case studies by keyword, business model, or acquisition channel to find comparable products and their documented strategies
- Retrieve full case details including pricing tiers, revenue disclosures, acquisition operations, and source URLs to cite when discussing indie product business practices
Tools this server exposes
| Tool | Does |
|---|---|
| search_cases | Search 43 audited products by keyword, category, business model, or acquisition channel |
| get_case | Retrieve full case details including pricing tiers, revenue disclosures, acquisition operations, and source URLs for every claim |
| pricing_benchmarks | Get median first paid tier, free-tier prevalence, and paywall-capability distribution computed from published pricing pages |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.