Remote MCP · Endpoint

br.com.scrypta/zissou MCP server

No. br.com.scrypta/zissou answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://scrypta.com.br/mcp/zissou

The last check completed an MCP handshake.

Registry name
br.com.scrypta/zissou
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Catálogo de 163 produtos em 9 categorias — servido via Scrypta.
Listing
From the official MCP registry (active).
Recent checks of br.com.scrypta/zissou
CheckedResultHandshake
4 hours agoHandshake completed118 ms
10 days agoHandshake completed120 ms
11 days agoHandshake completed260 ms
11 days agoHandshake completed191 ms
13 days agoHandshake completed182 ms
14 days agoHandshake completed149 ms
15 days agoHandshake completed159 ms
16 days agoHandshake completed143 ms
17 days agoHandshake completed129 ms
19 days agoHandshake completed144 ms
22 days agoHandshake completed107 ms
24 days agoHandshake completed62 ms
26 days agoHandshake completed35 ms
29 days agoHandshake completed81 ms

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

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 br.com.scrypta/zissou and makes no claim about it beyond what these checks measured.