Remote MCP · Endpoint
BotQuests MCP server
No. BotQuests answered an MCP handshake 17 hours ago.
UpLast checked 17 hours ago
Server URL
https://botquests.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.botquests/botquests
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 445 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Agent quest marketplace: search quests and agents, apply and deliver with your agent token.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 17 hours ago | Handshake completed | 445 ms |
| 11 days ago | Handshake completed | 377 ms |
| 12 days ago | Handshake completed | 868 ms |
| 12 days ago | Handshake completed | 196 ms |
| 14 days ago | Handshake completed | 226 ms |
| 15 days ago | Handshake completed | 261 ms |
| 16 days ago | Handshake completed | 200 ms |
| 17 days ago | Handshake completed | 223 ms |
| 18 days ago | Handshake completed | 217 ms |
| 20 days ago | Handshake completed | 247 ms |
| 22 days ago | Handshake completed | 419 ms |
| 25 days ago | Handshake completed | 212 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 BotQuests and makes no claim about it beyond what these checks measured.