Remote MCP · Endpoint

Ask My Envoy MCP server

No. Ask My Envoy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.askmyenvoy.com/mcp

The last check completed an MCP handshake.

Registry name
com.askmyenvoy/meeting-scheduling-coordination
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
491 ms
Tools exposed
1 tool
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Discover meeting-coordination Envoys. Work in progress; identity discovery is coming soon.
Listing
From the official MCP registry (active).
Recent checks of Ask My Envoy
CheckedResultHandshake
1 hour agoHandshake completed491 ms
2 days agoHandshake completed450 ms
4 days agoHandshake completed471 ms
6 days agoHandshake completed414 ms
8 days agoHandshake completed409 ms
9 days agoHandshake completed434 ms
11 days agoHandshake completed408 ms
12 days agoHandshake completed414 ms
13 days agoHandshake completed427 ms
16 days agoHandshake completed410 ms
17 days agoHandshake completed412 ms
19 days agoHandshake completed409 ms
20 days agoHandshake completed1.15 s
22 days agoHandshake completed443 ms
23 days agoFailed - the hostname does not resolve—

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