# Co-Founder Synergy Prover MCP MCP

> Co-Founder Synergy Prover runs your founding team structure against five critical axes of failure. It forces you to define vesting terms, separate core skills, establish tie-breaker authority for deadlocks, justify equity by measured contribution (time, risk, IP), and prove a verifiable execution velocity. If you're relying on trust or 'fairness,' this MCP tells you where your partnership will fail.

## Overview
- **Category:** strategy
- **Price:** Free
- **Tags:** co-founder, equity, vesting, startup, partnership, yc, cap-table

## Description

This MCP lets your agent evaluate the legal and operational structure of any founding team. It doesn't care how good people are; it only cares about whether the paperwork supports the business plan. You feed it a description of your co-founders, their roles, and your current agreements. The tool then runs an audit against five common failure points: vesting protection, skill separation, conflict resolution, equity justification, and shipping speed. It forces you to move past polite handshakes and into concrete legal structures. When you use this MCP via Vinkius, your agent generates a verdict that tells you if the partnership is structurally sound or if it contains fatal gaps—like having two CEOs who both 'manage' but nobody owns accountability. The result is a clear mandate: what needs to change before you even write the first line of code.

## Tools

### validate_co_founder_synergy
Runs a structured audit on your founding team to verify legal protections across vesting, skills, conflict resolution, equity contribution, and execution velocity.

## Prompt Examples

**Prompt:** 
```
We trust each other, 50/50, we both manage, we always agree, still in stealth mode.
```

**Response:** 
```
CLIFF_ABSENT — Five fatal gaps: no vesting, skill overlap, deadlock, equity politeness, zero velocity.
```

**Prompt:** 
```
4y vesting, 1y cliff. CTO builds, CEO sells. CEO decides after 48h. 60/40 by contribution. MVP week 4, 10 users week 8, weekly deploys.
```

**Response:** 
```
SYNERGY_PROVEN — Partnership validated. All axes pass. Execute.
```

**Prompt:** 
```
Technical co-founder wants to rebuild the entire backend (6 months). Business co-founder wants to launch in 3 markets simultaneously (needs current backend). Both have valid points. Equity is 50/50.
```

**Response:** 
```
Classic build-vs-ship tension. Neither is wrong — the conflict reveals missing decision framework. Define: what is the technical debt cost of NOT rebuilding? What is the market cost of NOT launching? Make the tradeoff quantitative, not emotional. Set a 90-day compromise: launch 1 market on current backend while scoping modular rebuild.
```

## Capabilities

### Audit vesting schedule
Validates if the founder equity structure includes mandatory 4-year vesting and a 1-year cliff, preventing premature asset forfeiture.

### Separate skill accountability
Distinguishes between complementary skills and mutually exclusive roles, ensuring clear ownership of building versus selling.

### Establish deadlock resolution
Defines a single CEO with defined strategic tie-breaker authority to prevent the partnership from stalling during conflict.

### Quantify equity contribution
Calculates founder shares based on measurable inputs: time spent, capital risked, intellectual property brought, not simply 'fairness'.

### Prove execution velocity
Checks for concrete shipping milestones—like MVP launch dates or user counts—to ensure the plan is moving faster than procrastination.

## Use Cases

### The 'Handshake' Founding Team
Two founders met and agreed to a 50/50 split based on 'mutual respect.' Your agent runs the validation, immediately returning CLIFF_ABSENT—telling you that without defined vesting schedules, the agreement is worthless if one founder bails after six months.

### The Overlapping Roles
The CTO and CEO both claim they 'manage product strategy.' Your agent identifies SKILL_OVERLAP. It forces you to define who has final say on the tech stack versus who handles market positioning, eliminating operational confusion.

### The Procrastinating Founders
The team spends six months 'perfecting the plan' and running internal meetings instead of shipping. The agent detects VELOCITY_ABSENT and forces you to set a concrete milestone: MVP by week 4, paying users by week 8.

### The Undefined Conflict
Disagreement erupts over the pivot direction. Without clear authority, the founders deadlock. The MCP mandates a defined CEO with strategic tie-breaker power, providing the necessary exit mechanism for the dispute.

## Benefits

- It forces you to think like a VC, demanding proof of concept instead of accepting vague promises. You get the actionable feedback needed to fix fatal structural flaws in your founding team.
- Stop relying on generalized 'fairness.' The tool calculates equity based specifically on measurable inputs: time invested, capital brought, and IP contributed, giving you a rationale that holds up legally.
- The MCP identifies Skill Overlap. It separates roles into mutual accountability—one person builds the product; another sells it. If both 'manage,' nobody is accountable for output.
- You don't need to wait for a disagreement. The tool forces you to define the escalation protocol and name a CEO with tie-breaker authority, so when conflict hits, you have a defined path forward.
- It prevents Cliff Blindness by mandating 4-year vesting schedules with specific forfeiture terms, protecting both parties if someone leaves early.

## How It Works

The bottom line is, you get an immediate, objective audit report that flags every structural flaw in your partnership agreement.

1. Input all founding details: roles, initial agreements, equity splits, and planned timelines into your agent.
2. Your agent sends this data to the MCP for validation across vesting, skills, conflict, equity, and velocity axes.
3. The tool returns a definitive verdict—either SYNERGY_PROVEN or one of five specific structural failure codes (e.g., CLIFF_ABSENT).

## Frequently Asked Questions

**How does the Co-Founder Synergy Prover validate vesting?**
It validates if your equity structure includes a 4-year vesting period and a 1-year cliff. If those terms are missing, it flags CLIFF_ABSENT because handshake agreements don't protect you legally.

**Can I use validate_co_founder_synergy if my co-founders work in different fields?**
Yes. The tool is designed to separate skills into mutually exclusive accountability domains (Builder vs Seller). It ensures that while your skills are diverse, their daily roles remain distinct.

**Is the Co-Founder Synergy Prover just for legal teams?**
No. While the output is highly technical, it's built for founders. It translates complex legal risks into simple action items you need to discuss with your co-founders immediately.

**What happens if I get SYNERGY_PROVEN?**
It means the current structure passes all five major structural tests. The tool validates that your team has defined rules for vesting, roles, conflict, equity, and velocity. You're ready to execute.

**What kind of information should I provide to `validate_co_founder_synergy`?**
The tool requires a comprehensive narrative covering all five axes: vesting, roles, conflict protocols, contributions, and shipping proof. The agent analyzes the entire structural picture, not just isolated facts.

**If my co-founder structure is unclear, how does `validate_co_founder_synergy` handle ambiguity?**
The MCP doesn't guess; it flags specific structural failures. If your input lacks a mechanism (like a tie-breaker or vesting schedule), the tool will return an explicit warning like DEADLOCK_RISK.

**Are there usage limits for running `validate_co_founder_synergy`?**
Vinkius manages general service rate limits. You can run it repeatedly during planning, but always check the Vinkius dashboard for specific quota details related to the MCP.

**Do I need advanced setup or permissions before using `validate_co_founder_synergy`?**
No. Since this MCP is free on Vinkius, you only need your AI client connected and authorized for basic tool invocation to start validating.

**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.

**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.

**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.