Remote MCP · Endpoint

Zernote MCP server

No. Zernote answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://zernote.com/mcp

The last check completed an MCP handshake.

Registry name
com.zernote/zernote
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
578 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
User research workspace to transcribe interviews and turn conversations into insights.
Listing
From the official MCP registry (active).
Recent checks of Zernote
CheckedResultHandshake
5 hours agoHandshake completed578 ms
2 days agoHandshake completed802 ms
4 days agoHandshake completed591 ms
5 days agoHandshake completed629 ms
7 days agoHandshake completed684 ms
8 days agoHandshake completed566 ms
9 days agoHandshake completed628 ms
12 days agoHandshake completed1.31 s
13 days agoHandshake completed739 ms
15 days agoHandshake completed552 ms
16 days agoHandshake completed667 ms
17 days agoHandshake completed643 ms
18 days agoHandshake completed659 ms
19 days agoHandshake completed666 ms
20 days agoHandshake completed661 ms
21 days agoHandshake completed910 ms
22 days agoCredentials required—

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

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