Remote MCP · Endpoint

Goatcade MCP server

Yes, as of 2 hours ago: the check failed for an unclassified reason.

DownLast checked 2 hours ago

Server URL

https://goatcade.com/mcp

The last check failed: the check failed for an unclassified reason.

Registry name
com.goatcade/arcade
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Real, free browser games that open in the chat: city builder, racer, horde shooter, deckbuilder.
Listing
From the official MCP registry (active).
Recent checks of Goatcade
CheckedResultHandshake
2 hours agoFailed - the check failed for an unclassified reason—
10 days agoHandshake completed83 ms
11 days agoHandshake completed184 ms
11 days agoHandshake completed159 ms
13 days agoHandshake completed82 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed137 ms
16 days agoHandshake completed199 ms
17 days agoHandshake completed81 ms
19 days agoHandshake completed348 ms
22 days agoHandshake completed74 ms
24 days agoHandshake completed98 ms
26 days agoHandshake completed76 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 Goatcade and makes no claim about it beyond what these checks measured.