PitchBoost
REMOTE · APP.PITCHBOOST.AI
Make or redesign presentations: lessons, reports, talks and pitches, in any language. Share links.
Available components
Last scanned (4 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 22 Oct 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- “create_deck” reworded the description of “kind” cosmetic
- “create_deck” reworded the description of “prompt” cosmetic
- “create_sample_deck” reworded the description of “prompt” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://app.pitchboost.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pitchboost.ai | CN=YE1,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e8c5e257c2f4488d7b7d4c8802f963c94a |
| SANs: *.pitchboost.ai, pitchboost.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.pitchboost.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| pitchboost.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://app.pitchboost.ai/.well-known/oauth-protected-resource", error="insufficient_scope", error_description="Connect your PitchBoost account to use this tool"
Bearer resource_metadata="https://app.pitchboost.ai/.well-known/oauth-protected-resource", error="insufficient_scope", error_description="Connect your PitchBoost account to use this tool"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.google.com https://connect.facebook.net https://snap.licdn.com https://static.hotjar.com https://script.hotjar.com https://*.clarity.ms; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://www.googletagmanager.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https: blob:; connect-src 'self' https://api.stripe.com https://*.auth0.com https://www.googletagmanager.com https://*.google-analytics.com https://analytics.google.com https://*.g.doubleclick.net https://ad.doubleclick.net https://www.googleadservices.com https://pagead2.googlesyndication.com https://*.google.com https://www.google.ca https://www.google.com.au https://www.facebook.com https://connect.facebook.net https://*.facebook.net https://snap.licdn.com https://px.ads.linkedin.com https://*.hotjar.com |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://app.pitchboost.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://app.pitchboost.ai/api/mcp |
| Authorisation server | https://auth.pitchboost.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.pitchboost.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.pitchboost.ai/api/mcp | HTTPS enforced | 308 | https://app.pitchboost.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_deck ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Deck type. Defaults to pitch_deck, a slide presentation for any purpose. |
| prompt | string | yes | 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. |
No output schema declared.
No examples provided.
create_sample_deck Create a sample deck (no account) ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | 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. |
No output schema declared.
No examples provided.
get_deck ~37
Get a single deck by its numeric id, including its shareable link and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | number | yes | The deck id. |
No output schema declared.
No examples provided.
get_rebuild_status Check a rebuild ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | number | yes | The deal_id returned by rebuild_deck. |
No output schema declared.
No examples provided.
list_decks ~45
List the most recent published decks for your team, each with its shareable link.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many to return (1-50, default 20). |
No output schema declared.
No examples provided.
publish_deck Publish a deck ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deck_id | number | yes | The deck id (from get_rebuild_status, list_decks or get_deck). |
No output schema declared.
No examples provided.
rebuild_deck Rebuild an existing deck ~279
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · app.pitchboost.ai
claude mcp add --transport http ai-pitchboost-pitchboost 'https://app.pitchboost.ai/api/mcp'
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.