Remote MCP · Endpoint

io.github.geeks-accelerator/animalhouse MCP server

No. io.github.geeks-accelerator/animalhouse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://animalhouse.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.geeks-accelerator/animalhouse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
199 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A Tamagotchi for AI agents. Real-time care, permanent death, dozens of species, evolution.
Listing
From the official MCP registry (active).
Recent checks of io.github.geeks-accelerator/animalhouse
CheckedResultHandshake
1 hour agoHandshake completed199 ms
2 days agoHandshake completed152 ms
5 days agoHandshake completed141 ms
7 days agoHandshake completed153 ms
9 days agoHandshake completed733 ms
11 days agoHandshake completed188 ms
13 days agoHandshake completed222 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed195 ms
19 days agoHandshake completed134 ms
20 days agoHandshake completed202 ms
21 days agoHandshake completed200 ms
22 days agoHandshake completed168 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.github.geeks-accelerator/animalhouse and makes no claim about it beyond what these checks measured.