ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Co-Founder Synergy Prover with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Two founders shook hands on 'we trust each other'. with no vesting cliff. It approved a 50/50 equity split out of politeness. It said 'we always agree' as conf

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 1 capability

The complete Co-Founder Synergy Prover capability set.

These are the exact actions your AI can choose when you ask it to work with Co-Founder Synergy Prover.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Co-Founder Synergy Prover.

  1. 01

    Validate co founder synergy

    Think like a YC partner evaluating a founding team. the #1 cause of startup death is co-founder conflict, and it is always structural. You must: (1) secure the CAP TABLE. 4-year vesting, 1-year cliff, monthly vesting after cliff, forfeiture terms, acceleration clauses. "We trust each other" is not a cap table strategy. Trust is necessary AND insufficient. legal structure protects both parties WHEN trust is tested, not IF, (2) separate SKILLS with MUTUALLY EXCLUSIVE ACCOUNTABILITY. who builds, who sells. Not "we complement each other". specific daily activities. CTO writes code daily. CEO runs customer calls daily. If both "manage," nobody is accountable for output, (3) break DEADLOCKS. name the CEO with strategic tie-breaker authority. Define domain authority: CEO decides strategy/hiring/fundraising, CTO decides architecture/tech-stack/engineering-process. Escalation protocol: if disagreement persists after 48h, CEO decides. "We always agree" is a fantasy. disagreement is inevitable and healthy IF there is a resolution mechanism, (4) justify EQUITY. calculate based on measurable contributions: time invested (full-time from when?), risk absorbed (salary foregone, savings invested), capital contributed ($X), IP brought (prototype, patents, domain expertise, network). "50/50 to be fair" is politeness, not a rationale. it creates resentment when one founder contributes more, (5) prove VELOCITY. show shipping evidence. MVP launched by week X. First Y paying users by week Z. Weekly deploys. Customer interviews per week. Pivots based on data. "Stealth mode" is death. you learn nothing without shipping. "Perfecting the plan" is procrastination. If rejected, the partnership has a fatal structural flaw. Structured reflection capability for YC-partner-level co-founder dynamics evaluation. Forces the agent to validate partnership structure with legal protections, mutually exclusive accountability, conflict resolution mechanisms, contribution-based equity, and shipping velocity. Catches Cliff Blindness (no vesting cliff. trusting handshakes instead of 4-year/1-year-cliff equity protection with forfeiture terms), Skill Overlap (two CEOs, no builder. "we both manage" means nobody is accountable), Deadlock Design (50/50 equity without tie-breaker authority. "we always agree" is a fantasy that kills startups), Equity Politeness (splitting 50/50 "to be fair" instead of calculating based on time, risk, capital, and IP contribution), and Velocity Absence ("stealth mode," perfecting the plan. no shipped product, no users, no data). Call once per founder team evaluation or partnership structure decision

Observed, not estimated

869ms average. Fast in production.

Co-Founder Synergy Prover is checked daily against the live service.

Daily averagePeak 1023ms
Aug 20Today
Fastest day
664ms
Slowest day
1023ms
14-day trend
Slowing+12%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Co-Founder Synergy Prover, so you can see the experience inside your AI.

It does not authenticate your account with Co-Founder Synergy Prover. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Co-Founder Synergy Prover Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_8FSyH9naKpwjVMD9A6XOdugcpDDLxVPDBqr7YFm6/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Co-Founder Synergy Prover capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "co-founder-synergy-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_8FSyH9naKpwjVMD9A6XOdugcpDDLxVPDBqr7YFm6/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Co-Founder Synergy Prover owners ask.

  • 01

    Why does it reject 'we trust each other'?

    Trust is not a cap table strategy. Without vesting, a co-founder can leave in month 2 with half the company. Mandate 4-year vesting, 1-year cliff.

  • 02

    Why is 50/50 considered naive?

    50/50 is politeness, not math. When one founder works full-time and the other part-time, equity must reflect actual contribution. time, risk, capital, IP.

  • 03

    What is 'Velocity Absent'?

    Strong alignment but zero shipping. Stuck in stealth mode. Launch now, iterate tomorrow. Show MVP date, first 10 users, deployment frequency.