# PitchBoost (remote · app.pitchboost.ai)

Make or redesign presentations: lessons, reports, talks and pitches, in any language. Share links.

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.pitchboost.ai`: 90/100 (this document), [markdown](https://verifymcp.io/servers/ai-pitchboost-pitchboost/api-mcp.md), [page](https://verifymcp.io/servers/ai-pitchboost-pitchboost/api-mcp)

## Channel facts

- Endpoint: `https://app.pitchboost.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.1`

## 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-05.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 892 tokens (~127/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**: 67/100
  - Stability observed for 20 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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 PitchBoost MCP server?

PitchBoost is a hosted endpoint at https://app.pitchboost.ai/api/mcp, 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 ai-pitchboost-pitchboost 'https://app.pitchboost.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-pitchboost-pitchboost": {
      "url": "https://app.pitchboost.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-pitchboost-pitchboost": {
      "type": "http",
      "url": "https://app.pitchboost.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-pitchboost-pitchboost]
url = "https://app.pitchboost.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-pitchboost-pitchboost": {
      "type": "remote",
      "url": "https://app.pitchboost.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-pitchboost-pitchboost --url 'https://app.pitchboost.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-pitchboost-pitchboost:
    url: "https://app.pitchboost.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-pitchboost-pitchboost": {
      "Transport": "http",
      "Url": "https://app.pitchboost.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-pitchboost-pitchboost -t streamable-http -u 'https://app.pitchboost.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-pitchboost-pitchboost": {
      "type": "http",
      "url": "https://app.pitchboost.ai/api/mcp"
    }
  }
}
```

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-05 (score 90, +1)

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

### 2026-11-03 (score 89, +1)

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

### 2026-11-01 (score 88, +1)

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

### 2026-10-29 (score 87, +1)

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

### 2026-10-27 (score 86, +1)

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

### 2026-10-25 (score 85, +1)

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

### 2026-10-23 (score 84, +1)

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

### 2026-10-22 (score 83, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_deck” rewrote its description, which is the text the model reads
- [security] Tool “create_sample_deck” rewrote its description, which is the text the model reads
- [security] Tool “rebuild_deck” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “create_deck” reworded the description of “kind”
- [cosmetic] “create_deck” reworded the description of “prompt”
- [cosmetic] “create_sample_deck” reworded the description of “prompt”

## MCP tools (7)

### `create_sample_deck` (~152 tokens)

Create a sample deck (no account)

Make a hosted, shareable presentation from a short prompt with no PitchBoost account: a lesson or lecture, a class or thesis presentation, a report or update, a talk, or a sales or investor pitch, in any language. The deck carries a small PitchBoost badge and the response includes a single-use claim token the user can enter after signing in to move the deck into their own account. Use this when the user has not connected PitchBoost. Generation takes up to a minute.

Input parameters:

- `prompt` (string, required): What the presentation is about, who will see it, and what it should achieve. For a pitch, include the company, the offer and the prospect. Up to 1000 characters.

### `create_deck` (~127 tokens)

Make a presentation in the user's PitchBoost account from a prompt: a lesson or lecture, a class or thesis presentation, a report or update, a talk or workshop, or a sales or investor pitch, in any language. Returns a shareable link. Generation takes up to ~60 seconds.

Input parameters:

- `kind` (string): Deck type. Defaults to pitch_deck, a slide presentation for any purpose.
- `prompt` (string, required): What the presentation is about, who will see it, and what it should achieve. For a pitch, include the company, the offer and the prospect.

### `rebuild_deck` (~279 tokens)

Rebuild an existing deck

Improve, redesign, polish or rebrand an existing presentation of any kind (coursework, a lecture, a report, a pitch) in any language. Pass the text of every slide of the user's uploaded PowerPoint, Google Slides or Keynote deck (title and body, in order). PitchBoost keeps the content and figures, rebuilds every slide with professional layout in the user's brand, checks every number against the source, and returns a shareable link (the PowerPoint and PDF download from the web app). Generation runs in the background for 2 to 4 minutes: this call returns a deal_id at once; call get_rebuild_status with it to get the link when ready.

Input parameters:

- `deal_name` (string): Optional name for the deck in the user's dashboard. Defaults to the first slide title.
- `instructions` (string): Optional guidance from the user, for example the audience, tone, or slides to emphasise. Up to 1000 characters.
- `mode` (string): preserve (default) keeps one slide per source slide; condense compresses a long deck to about 10 to 15 slides.
- `slides` (array, required): The source deck, one entry per slide in order. Extract these from the user's uploaded file: title is the slide heading if any, body is all other text on the slide.

### `get_rebuild_status` (~60 tokens)

Check a rebuild

Check whether a rebuild started with rebuild_deck has finished. Returns the shareable link and editor link when the deck is ready, or how long it has been running.

Input parameters:

- `deal_id` (number, required): The deal_id returned by rebuild_deck.

### `publish_deck` (~82 tokens)

Publish a deck

Turn a deck's shareable link on. Rebuilt and generated decks go live at their share_url as soon as they are finished; use this when the user made one private and wants the link back. Not destructive and safe to repeat.

Input parameters:

- `deck_id` (number, required): The deck id (from get_rebuild_status, list_decks or get_deck).

### `list_decks` (~45 tokens)

List the most recent published decks for your team, each with its shareable link.

Input parameters:

- `limit` (number): How many to return (1-50, default 20).

### `get_deck` (~37 tokens)

Get a single deck by its numeric id, including its shareable link and metadata.

Input parameters:

- `deck_id` (number, required): The deck id.

## Diagnostics

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

## Score history

- 2026-11-05: 90
- 2026-11-04: 89
- 2026-11-03: 89
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 87
- 2026-10-30: 87
- 2026-10-29: 87
- 2026-10-28: 86
- 2026-10-27: 86
- 2026-10-26: 85
- 2026-10-25: 85
- 2026-10-24: 84
- 2026-10-23: 84
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 82
- 2026-10-18: 82
- 2026-10-17: 81
- 2026-10-16: 81

## Common questions

### What is the PitchBoost MCP server?

PitchBoost is an MCP server listed in the public MCP registry as ai.pitchboost/pitchboost. Make or redesign presentations: lessons, reports, talks and pitches, in any language. Share links. This page covers its hosted endpoint (https://app.pitchboost.ai/api/mcp).

### Is the PitchBoost MCP server safe to use?

PitchBoost scores 90 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 PitchBoost MCP server expose?

PitchBoost exposes 7 tools: create_sample_deck, create_deck, rebuild_deck, get_rebuild_status, publish_deck, and 2 more. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.

### Does the PitchBoost MCP server require authentication?

Yes. PitchBoost asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the PitchBoost MCP server still maintained?

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

## Links

- Remote endpoint: https://app.pitchboost.ai/api/mcp
- Website: https://pitchboost.ai/features/api-and-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-pitchboost-pitchboost/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-pitchboost-pitchboost/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-pitchboost-pitchboost/api-mcp