Remote MCP · Endpoint

Zacatrus MCP server

No. Zacatrus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://zacatrus.es/mcp

The last check completed an MCP handshake.

Registry name
es.zacatrus/zacatrus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Juegos de mesa Zacatrus: busca y compra, stock en tiendas, reserva de mesa, eventos y tu cuenta.
Listing
From the official MCP registry (active).
Recent checks of Zacatrus
CheckedResultHandshake
1 hour agoHandshake completed293 ms
1 day agoHandshake completed209 ms
2 days agoHandshake completed292 ms
3 days agoHandshake completed251 ms
4 days agoHandshake completed291 ms
5 days agoHandshake completed263 ms
6 days agoHandshake completed316 ms
8 days agoHandshake completed300 ms
11 days agoHandshake completed260 ms
13 days agoHandshake completed290 ms
16 days agoHandshake completed290 ms
18 days agoHandshake completed253 ms
20 days agoHandshake completed267 ms
22 days agoHandshake completed278 ms
24 days agoHandshake completed279 ms

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

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