# Pitch Protocol (remote · api.pitchprotocol.vc)

Apply to Pitch Protocol, a pre-seed and seed investor, from your AI agent. Free, no web form.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.pitchprotocol.vc`: 64/100 (this document), [markdown](https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder.md), [page](https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder)

## Channel facts

- Endpoint: `https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_answers).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2245 tokens (~320/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pitch Protocol MCP server?

Pitch Protocol is a hosted endpoint at https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http vc-pitchprotocol-founder 'https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry'
```

### Cursor

```json
{
  "mcpServers": {
    "vc-pitchprotocol-founder": {
      "url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vc-pitchprotocol-founder": {
      "type": "http",
      "url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vc-pitchprotocol-founder]
url = "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vc-pitchprotocol-founder": {
      "type": "remote",
      "url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vc-pitchprotocol-founder --url 'https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vc-pitchprotocol-founder:
    url: "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
```

### Netclaw

```json
{
  "McpServers": {
    "vc-pitchprotocol-founder": {
      "Transport": "http",
      "Url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vc-pitchprotocol-founder -t streamable-http -u 'https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry'
```

### Other

```json
{
  "mcpServers": {
    "vc-pitchprotocol-founder": {
      "type": "http",
      "url": "https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 62)

First indexed and scored.

## MCP tools (7)

### `submit_answers` (~439 tokens)

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 parameters:

- `answers` (array, required): Array of `{questionId, answer}` objects. Can be empty when finalize is true.
- `applicationId` (string, required): Application id from `create_application`.
- `finalize` (boolean): If true, commits the answers and flips status to submitted. One-way — confirm with founder first.

Output parameters:

- `result` (string)

### `get_application_schema` (~86 tokens)

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

Output parameters:

- `result` (string)

### `create_application` (~310 tokens)

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 parameters:

- `contactEmail` (string, required): Email where the 6-digit verification code will be sent. Must be the founder's real address.
- `payload` (string, required): Full PitchApplication JSON payload. Call `get_application_schema` for field list + limits.
- `submittedBy` (string, required): 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.

Output parameters:

- `result` (string)

### `verify_email` (~284 tokens)

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 parameters:

- `applicationId` (string, required): Application id from `create_application`.
- `code` (string, required): The 6-digit numeric code from the founder's inbox.

Output parameters:

- `result` (string)

### `update_application` (~302 tokens)

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 parameters:

- `applicationId` (string, required): Application id from `create_application`.
- `contactEmail` (string|null): New contact email (optional). Resets verification and issues a new code.
- `payload` (string|null): Full PitchApplication JSON (optional). Replaces the current payload wholesale.
- `responseFormat` (string): `markdown` (default) or `json`. JSON returns the raw StatusView for programmatic use.

Output parameters:

- `result` (string)

### `get_status` (~382 tokens)

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 parameters:

- `applicationId` (string, required): Application id from `create_application`.
- `responseFormat` (string): `markdown` (default) or `json`. JSON returns the raw StatusView for programmatic use.

Output parameters:

- `result` (string)

### `resend_verification` (~154 tokens)

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 parameters:

- `applicationId` (string, required): Application id from `create_application`.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder#diagnostics

## Score history

- 2026-11-21: 64
- 2026-11-20: 64
- 2026-11-19: 63
- 2026-11-18: 63
- 2026-11-17: 62

## Common questions

### What is the Pitch Protocol MCP server?

Pitch Protocol is an MCP server listed in the public MCP registry as vc.pitchprotocol/founder. Apply to Pitch Protocol, a pre-seed and seed investor, from your AI agent. Free, no web form. This page covers its hosted endpoint (https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry).

### Is the Pitch Protocol MCP server safe to use?

Pitch Protocol scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pitch Protocol MCP server expose?

Pitch Protocol exposes 7 tools: submit_answers, get_application_schema, create_application, verify_email, update_application, and 2 more. Their descriptions and schemas cost roughly 1,957 tokens of context every time the server is loaded.

### Does the Pitch Protocol MCP server require authentication?

No. We connected to Pitch Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pitch Protocol MCP server still maintained?

Pitch Protocol is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Pitch Protocol MCP server?

VerifyMCP ran 13 checks on Pitch Protocol, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.pitchprotocol.vc/mcp/founder?ppr=ppc_mcpregistry
- Website: https://www.pitchprotocol.vc/?utm_source=mcp-registry&utm_medium=listing&utm_campaign=mcp-directories
- Changelog RSS feed: https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder.xml
- Changelog JSON feed: https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder.json
- HTML version of this page: https://verifymcp.io/servers/vc-pitchprotocol-founder/mcp-founder
