Remote MCP · Endpoint

Book a Sponsor MCP server

No. Book a Sponsor answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bookasponsor.com/mcp

The last check completed an MCP handshake.

Registry name
com.bookasponsor/book-a-sponsor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
296 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find brands that already sponsor newsletters like yours, with sponsorship rates.
Website
https://bookasponsor.com/
Listing
From the official MCP registry (active).
Recent checks of Book a Sponsor
CheckedResultHandshake
1 hour agoHandshake completed296 ms
1 day agoHandshake completed334 ms
4 days agoHandshake completed293 ms
6 days agoHandshake completed303 ms
9 days agoHandshake completed304 ms
11 days agoHandshake completed299 ms
13 days agoHandshake completed323 ms
15 days agoHandshake completed294 ms
17 days agoHandshake completed340 ms
19 days agoHandshake completed303 ms
21 days agoHandshake completed304 ms
22 days agoHandshake completed296 ms
23 days agoHandshake completed304 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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