Remote MCP · Endpoint

Grandpa's AI MCP server

No. Grandpa's AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://grandpasai.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.wescorp/grandpasai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
761 ms
Tools exposed
5 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Search Grandpa's AI research on age reversal, robotics, AI, and space — 5 read-only MCP tools.
Listing
From the official MCP registry (active).
Recent checks of Grandpa's AI
CheckedResultHandshake
1 hour agoHandshake completed761 ms
2 days agoHandshake completed286 ms
5 days agoHandshake completed277 ms
7 days agoHandshake completed319 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed402 ms
13 days agoHandshake completed302 ms
15 days agoHandshake completed281 ms
17 days agoHandshake completed294 ms
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed535 ms
21 days agoHandshake completed270 ms
23 days agoHandshake completed398 ms

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

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