Remote MCP · Endpoint

Sissoo MCP server

No. Sissoo answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://sissoo.com/mcp

The last check completed an MCP handshake.

Registry name
com.sissoo/finder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
340 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find wellbeing sessions with independent practitioners: free times, prices and booking links.
Listing
From the official MCP registry (active).
Recent checks of Sissoo
CheckedResultHandshake
20 minutes agoHandshake completed340 ms
3 days agoHandshake completed323 ms
14 days agoHandshake completed407 ms
14 days agoHandshake completed393 ms
15 days agoHandshake completed364 ms
16 days agoHandshake completed334 ms
18 days agoHandshake completed337 ms
18 days agoHandshake completed371 ms
19 days agoHandshake completed337 ms
21 days agoHandshake completed350 ms
23 days agoHandshake completed407 ms
25 days agoHandshake completed332 ms
28 days agoHandshake completed317 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 Sissoo and makes no claim about it beyond what these checks measured.