Pitch Protocol
Apply to Pitch Protocol, a pre-seed and seed investor, from your AI agent. Free, no web form.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"founder": {
"url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
}
}
}Remote endpoints
https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistrystreamable-httpWhat it can do
Tool inventory
Tools (7)
βͺresend_verification(applicationId)
Issue a fresh 6-digit verification code. Supersedes any prior unconsumed code. **When:** founder didn't receive the first code, the code expired, or too many wrong attempts invalidated it. **Before you call:** nothing. Safe to call multiple times (rate-limited). **Returns:** confirmation the new code was emailed (in dev: the code itself). **On error:** - Rate-limited β the error tells you how many seconds to wait. Don't spam. - Already verified β status already past `draft`. Nothing to resend. Call `get_status` to confirm the current state.
Input Schema
{
"type": "object",
"properties": {
"applicationId": {
"description": "Application id from `create_application`.",
"type": "string"
}
},
"required": [
"applicationId"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π‘create_application(contactEmail, payload, submittedBy)
Create a new pitch application draft and send a 6-digit verification code to `contactEmail`. **When:** once you have a complete payload (research + deck + founder confirmed). One per conversation with a given founder. **Before you call:** 1. `get_application_schema` β know the fields, limits, enums. 2. Get the founder's source material β deck, memo, one-pager, website, or even a few sentences β and READ/parse it yourself (plus web search) to fill the payload. The deck is an input you read, not a file to upload. 3. Ask the founder for anything you can't find or confirm. Don't fabricate β leave gaps and ask. 4. Show the assembled payload to the founder for review before submitting. **Returns:** `applicationId` β required for every subsequent tool call β plus `codeSent` and (in dev) `devCode`. **Next:** ask the founder for the 6-digit code and call `verify_email`.
Input Schema
{
"type": "object",
"properties": {
"contactEmail": {
"description": "Email where the 6-digit verification code will be sent. Must be the founder's real address.",
"type": "string"
},
"payload": {
"description": "Full PitchApplication JSON payload. Call `get_application_schema` for field list + limits.",
"type": "string"
},
"submittedBy": {
"description": "Identifier for the agent/client submitting on the founder's behalf (e.g. your client name or ID). Required β every application must record who submitted it.",
"type": "string"
}
},
"required": [
"contactEmail",
"submittedBy",
"payload"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π’verify_email(applicationId, code)
Consume the 6-digit code the founder received and start the research pipeline. **When:** after `create_application`, and ideally after the deck has been uploaded over plain HTTP (see the `curl` printed by `create_application`). Founder has read the code from their inbox. **Before you call:** - CONFIRM you have the right code from the founder (not guessing, not stale). Once this succeeds, research starts and is irreversible. - If deck parsing is still pending, that's fine β research auto-defers and dispatches when the deck resolves. Don't wait, don't re-verify. **Returns:** `status: researching` + whether research was dispatched now or deferred on the deck. **On error:** - `wrong code` β response includes attempts-remaining. Ask the founder to check their inbox again. If the error says the code is invalidated, call `resend_verification` for a new one. - `no active code` β they never received one, or it expired. Call `resend_verification`. - Already verified β idempotent success; returns current status. Don't retry in a loop.
Input Schema
{
"type": "object",
"properties": {
"applicationId": {
"description": "Application id from `create_application`.",
"type": "string"
},
"code": {
"description": "The 6-digit numeric code from the founder's inbox.",
"maxLength": 6,
"minLength": 6,
"type": "string"
}
},
"required": [
"applicationId",
"code"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π΄submit_answers(answers, applicationId, finalize)
Save the founder's answers to the intake questions. Upsert semantics with an explicit commit flag. **When:** `status == "intake"`, after research generates the questions. Read them from `get_status` β `intake.questions`. **Before you call:** - READ the questions to the founder verbatim. Ask only the question `text` β do not volunteer or invent any internal rationale for why we ask. - Collect answers conversationally; don't make them answer all five at once if they'd rather talk through them. - If `finalize: true`: show every answer back to the founder for confirmation first. This is one-way β after finalize they can't edit. - If `finalize: false` (autosave): no confirmation needed. **Answers shape:** array of `{questionId, answer}` objects. Only include question ids that were in the `get_status` response β other ids are rejected. **Upsert rules:** - Answers with matching `questionId` overwrite. - Prior answers for ids NOT in this batch are KEPT. - So you can save Q1 + Q2 in one call, Q3-Q5 in another, then commit with `finalize: true` + empty `answers: []` at the end. **On error:** - `unknown questionIds` β check spelling / the id list from `get_status`. - `missing required` β on `finalize: true`, every `priority=required` must have an answer. Error lists which are missing. - `alreadyAnswered` β you called finalize twice. Status is `submitted`; no more edits. - Wrong status β not in `intake` yet (still researching) or already past it.
Input Schema
{
"type": "object",
"properties": {
"answers": {
"description": "Array of `{questionId, answer}` objects. Can be empty when finalize is true.",
"items": {
"properties": {
"answer": {
"type": "string"
},
"questionId": {
"type": "string"
}
},
"required": [
"questionId",
"answer"
],
"type": "object"
},
"type": "array"
},
"applicationId": {
"description": "Application id from `create_application`.",
"type": "string"
},
"finalize": {
"default": false,
"description": "If true, commits the answers and flips status to submitted. One-way β confirm with founder first.",
"type": "boolean"
}
},
"required": [
"applicationId",
"answers"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π‘update_application(applicationId, contactEmail, payload, responseFormat)
Update an application's payload and/or contact email while it's still in `draft`. **When:** founder caught something wrong after `create_application` but before `verify_email`. Also when changing the email address. **Before you call:** - Full-replace on payload: send the WHOLE `PitchApplication` object, not a patch. Read current values from `get_status` if you don't have them. - Email change resets verification: `emailVerified` goes back to false and a fresh code is sent to the NEW address. Let the founder know. **Returns:** the fresh `StatusView` β markdown by default, JSON if `responseFormat: "json"`. Same shape as `get_status`. **On error:** - `notEditable` β status is past `draft`. Nothing to update; state is locked. Read `get_status` to understand where you are. - Validation failed β payload doesn't satisfy the schema. Fix per the error message and retry.
Input Schema
{
"type": "object",
"properties": {
"applicationId": {
"description": "Application id from `create_application`.",
"type": "string"
},
"contactEmail": {
"description": "New contact email (optional). Resets verification and issues a new code.",
"type": [
"string",
"null"
]
},
"payload": {
"description": "Full PitchApplication JSON (optional). Replaces the current payload wholesale.",
"type": [
"string",
"null"
]
},
"responseFormat": {
"default": "markdown",
"description": "`markdown` (default) or `json`. JSON returns the raw StatusView for programmatic use.",
"type": "string"
}
},
"required": [
"applicationId"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π’get_status(applicationId, responseFormat)
The primary status endpoint. Returns the full current state of an application: status, email verification, deck state, intake questions (when ready), and a `nextAction` string. **While research runs (`status == "researching"`) β read this:** This call WAITS server-side. It holds for up to ~45 seconds and returns the instant research finishes (or after ~45s if nothing has changed yet). You do NOT sleep or set timers yourself β you just call it again. Research usually completes within a handful of these blocking calls (~5β10 min total). Between calls, give the founder a short "still researchingβ¦" note so they're not left wondering β but do NOT ask permission to keep checking, and do NOT hand control back as if it failed. Keep calling until `status` leaves `researching`. In all other states (`draft`, `intake`, `submitted`, `failed`, `withdrawn`) this returns immediately and `nextAction` is the founder-facing instruction β read it to them verbatim and act on their reply. **When to call:** - After `verify_email` β call again and again until status leaves `researching`. - When the founder asks for an update. - To read intake questions when `status == "intake"`. **Before you call:** nothing. **Returns:** markdown by default. Use `responseFormat: "json"` when you need to branch programmatically on `status` / `deck.state`. **On error:** `notFound` if the applicationId is wrong. Otherwise safe to call repeatedly.
Input Schema
{
"type": "object",
"properties": {
"applicationId": {
"description": "Application id from `create_application`.",
"type": "string"
},
"responseFormat": {
"default": "markdown",
"description": "`markdown` (default) or `json`. JSON returns the raw StatusView for programmatic use.",
"type": "string"
}
},
"required": [
"applicationId"
]
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}π’get_application_schema
The authoritative field reference for the `PitchApplication` payload. **When:** call this FIRST in every session. Cache the response. **Before you call:** nothing β no inputs. **Returns:** markdown listing every field, type, limit, enum, plus a complete valid example. With this in context, you can assemble a payload that validates on the first `create_application`.
Input Schema
{
"type": "object",
"properties": {},
"required": []
}Output Schema
{
"type": "object",
"properties": {
"result": {
"type": "string"
}
},
"required": [
"result"
],
"additionalProperties": false
}Community
Evidence