Remote MCP · Endpoint

My AI Guide MCP server

No. My AI Guide answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://myaiguide.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.myaiguide/myaiguide
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
129 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only access to the My AI Guide directory of AI tools, repos, plugins, news and guides.
Listing
From the official MCP registry (active).
Recent checks of My AI Guide
CheckedResultHandshake
8 hours agoHandshake completed129 ms
10 days agoHandshake completed136 ms
11 days agoHandshake completed164 ms
11 days agoHandshake completed162 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed110 ms
15 days agoHandshake completed344 ms
16 days agoHandshake completed207 ms
17 days agoHandshake completed103 ms
19 days agoHandshake completed133 ms
22 days agoHandshake completed161 ms
24 days agoHandshake completed124 ms
26 days agoHandshake completed163 ms
29 days agoHandshake completed140 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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