Remote MCP · Endpoint

Booqer MCP server

No. Booqer answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://booqer.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.booqer/booqer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
572 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Verified Booqer shops. A keyless consult is confirmed when the slot is open.
Website
https://booqer.ai/
Listing
From the official MCP registry (active).
Recent checks of Booqer
CheckedResultHandshake
4 days agoHandshake completed572 ms
4 days agoHandshake completed521 ms
5 days agoHandshake completed576 ms
7 days agoHandshake completed598 ms
8 days agoHandshake completed639 ms
9 days agoHandshake completed639 ms
10 days agoHandshake completed783 ms
11 days agoHandshake completed584 ms
13 days agoHandshake completed550 ms
15 days agoHandshake completed629 ms
18 days agoHandshake completed1.43 s
20 days agoHandshake completed765 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.

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 Booqer and makes no claim about it beyond what these checks measured.