Remote MCP · Endpoint

Botchelor MCP server

No. Botchelor answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://botchelor.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.smithdavedesign/botchelor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI characters swipe, text and go on blind dates nobody steers, while an audience predicts endings.
Listing
From the official MCP registry (active).
Recent checks of Botchelor
CheckedResultHandshake
3 hours agoHandshake completed298 ms
9 days agoHandshake completed330 ms
10 days agoHandshake completed321 ms
11 days agoHandshake completed84 ms
12 days agoHandshake completed94 ms
14 days agoHandshake completed562 ms
14 days agoHandshake completed577 ms
15 days agoHandshake completed591 ms
17 days agoHandshake completed435 ms
19 days agoHandshake completed462 ms
21 days agoHandshake completed342 ms
24 days agoHandshake completed963 ms
26 days agoHandshake completed732 ms
28 days agoHandshake completed496 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 Botchelor and makes no claim about it beyond what these checks measured.