Remote MCP · Endpoint

PitchBoost MCP server

No. PitchBoost answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://app.pitchboost.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.pitchboost/pitchboost
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Make or redesign presentations: lessons, reports, talks and pitches, in any language. Share links.
Listing
From the official MCP registry (active).
Recent checks of PitchBoost
CheckedResultHandshake
14 minutes agoHandshake completed303 ms
10 days agoHandshake completed264 ms
10 days agoHandshake completed195 ms
11 days agoHandshake completed1.22 s
13 days agoHandshake completed162 ms
14 days agoHandshake completed149 ms
14 days agoHandshake completed231 ms
15 days agoHandshake completed220 ms
17 days agoHandshake completed235 ms
19 days agoHandshake completed127 ms
21 days agoHandshake completed152 ms
24 days agoHandshake completed214 ms
26 days agoHandshake completed176 ms
28 days agoHandshake completed182 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with PitchBoost and makes no claim about it beyond what these checks measured.