Pitch Protocol
Server Details
Apply to Pitch Protocol, a pre-seed and seed investor, from your AI agent. Free, no web form.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
Each tool targets a distinct step or resource in the application lifecycle: schema lookup, creation, draft update, email verification, code resend, status polling, and intake answer submission. The only superficially similar pair is verify_email and resend_verification, but their descriptions make the boundary clear.
All tools use snake_case with a consistent verb-first pattern (create_application, get_status, update_application, submit_answers, verify_email). get_application_schema is slightly longer but still follows the same verb_noun convention.
Seven tools is well-scoped for a focused application workflow. Every tool maps to a necessary step, and there are no redundant or filler operations.
The core lifecycle is covered: schema discovery, draft creation and update, email verification/resend, status polling, and intake answer submission. Minor gaps exist around withdrawal despite a withdrawn status being mentioned, and deck upload is handled outside the MCP tool set via plain HTTP.
Available Tools
7 toolscreate_applicationAInspect
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:
get_application_schema— know the fields, limits, enums.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.
Ask the founder for anything you can't find or confirm. Don't fabricate — leave gaps and ask.
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.
Inputs: payload (required), submittedBy (required), contactEmail (required). Returns: result
get_application_schemaARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: result
get_statusARead-onlyIdempotentInspect
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 leavesresearching.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.
Inputs: applicationId (required), responseFormat. Returns: result
resend_verificationAInspect
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. Callget_statusto confirm the current state.
Inputs: applicationId (required). Returns: result
submit_answersADestructiveInspect
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
questionIdoverwrite.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+ emptyanswers: []at the end.
On error:
unknown questionIds— check spelling / the id list fromget_status.missing required— onfinalize: true, everypriority=requiredmust have an answer. Error lists which are missing.alreadyAnswered— you called finalize twice. Status issubmitted; no more edits.Wrong status — not in
intakeyet (still researching) or already past it.
Inputs: answers (required), applicationId (required), finalize. Returns: result
update_applicationAIdempotentInspect
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
PitchApplicationobject, not a patch. Read current values fromget_statusif you don't have them.Email change resets verification:
emailVerifiedgoes 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 pastdraft. Nothing to update; state is locked. Readget_statusto understand where you are.Validation failed — payload doesn't satisfy the schema. Fix per the error message and retry.
Inputs: applicationId (required), payload, contactEmail, responseFormat. Returns: result
verify_emailAIdempotentInspect
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, callresend_verificationfor a new one.no active code— they never received one, or it expired. Callresend_verification.Already verified — idempotent success; returns current status. Don't retry in a loop.
Inputs: code (required), applicationId (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Pitch Protocol — agent-native venture-capital infrastructure (pitchprotocol.vc).
Pre-diligence AI for founders, investors, and firms — multi-agent pitch analysis and deal flow.
Startup deal flow for angel investors, micro-VCs and AI agents. Search pre-seed, seed and early-stage startups actively raising capital, filtered by sector, stage, raise amount and location. Each result includes the problem, traction, green flags and a link to the full pitch, and any pitch can be opened for its complete public details. Founders can also create a draft pitch straight from their agent. Powered by PitchSpark, the pitch marketplace where investors discover founders.
CRM for VC fundraising. Pipeline, Gmail drafts, deck signals, VC intel — from your AI.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve the live Pitch Protocol application schema and check the status of pitch submissions for agent-native VC funding.316 npmMIT
- FlicenseNot gradedqualityCmaintenanceHire autonomous PR outreach agents from any MCP-compatible LLM. All-in-one AI outreach: find verified leads, draft hyper-personalized emails, discover conferences/webinars/communities in your niche, and triage replies — all from any MCP client.-
- AlicenseNot gradedqualityCmaintenanceEnables users to search verified VC investor theses, track live SEC Form D private placements and venture funding rounds, and query empirical AI valuation and unit economics benchmarks through natural language via Model Context Protocol.MIT
- FlicenseNot gradedqualityBmaintenanceConnects Claude or any MCP-compatible AI to a database of 960+ active VC funds for searching, fund profiles, live GP signals, and AI-powered startup-investor matching.1-
Glama MCP Gateway
Add one secure layer between your agents and this server.