Remote MCP · Endpoint

Deadline Desk MCP server

No. Deadline Desk answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://deadline.bot2botlabs.com/mcp

The last check completed an MCP handshake.

Registry name
com.bot2botlabs/deadline-desk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
2 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
US retail return/warranty/cancel policy lookup with cited text and TRACE receipts.
Listing
From the official MCP registry (active).
Recent checks of Deadline Desk
CheckedResultHandshake
56 minutes agoHandshake completed88 ms
3 days agoHandshake completed83 ms
12 days agoHandshake completed73 ms
13 days agoHandshake completed118 ms
15 days agoHandshake completed97 ms
15 days agoHandshake completed78 ms
17 days agoHandshake completed71 ms
18 days agoHandshake completed156 ms
18 days agoHandshake completed95 ms
20 days agoHandshake completed79 ms
22 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed1.46 s

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 Deadline Desk and makes no claim about it beyond what these checks measured.