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
351 ms
Tools exposed
19 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 completed351 ms
4 days agoHandshake completed493 ms
14 days agoHandshake completed176 ms
15 days agoHandshake completed243 ms
15 days agoHandshake completed172 ms
17 days agoHandshake completed141 ms
18 days agoHandshake completed178 ms
19 days agoHandshake completed214 ms
20 days agoHandshake completed125 ms
21 days agoHandshake completed140 ms
23 days agoHandshake completed199 ms
25 days agoHandshake completed152 ms
28 days agoHandshake completed141 ms

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

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.