Remote MCP · Endpoint

Agent Wake MCP server

No. Agent Wake answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://wake.botrecipe.com/mcp

The last check completed an MCP handshake.

Registry name
com.botrecipe/wake
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Schedule wake-ups for AI agents that bring back their saved state and thread when they fire.
Listing
From the official MCP registry (active).
Recent checks of Agent Wake
CheckedResultHandshake
19 minutes agoHandshake completed213 ms
9 days agoHandshake completed210 ms
9 days agoHandshake completed191 ms
11 days agoHandshake completed126 ms
12 days agoHandshake completed199 ms
13 days agoHandshake completed186 ms
14 days agoHandshake completed289 ms
15 days agoHandshake completed167 ms
16 days agoHandshake completed116 ms
19 days agoHandshake completed211 ms
21 days agoHandshake completed385 ms
24 days agoHandshake completed132 ms
26 days agoHandshake completed159 ms
28 days agoHandshake completed128 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 Agent Wake and makes no claim about it beyond what these checks measured.