Remote MCP · Endpoint

Nota MCP server

No. Nota answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nota-ryo.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.PugarHuda/nota
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
201 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only crypto research skills that check a price, RSI and ATR against independent sources.
Listing
From the official MCP registry (active).
Recent checks of Nota
CheckedResultHandshake
1 hour agoHandshake completed201 ms
2 days agoHandshake completed208 ms
4 days agoHandshake completed595 ms
5 days agoHandshake completed196 ms
7 days agoHandshake completed223 ms
8 days agoHandshake completed222 ms
9 days agoHandshake completed208 ms
12 days agoHandshake completed188 ms
13 days agoHandshake completed209 ms
15 days agoHandshake completed2.79 s
17 days agoHandshake completed198 ms
18 days agoHandshake completed206 ms
19 days agoHandshake completed219 ms
20 days agoHandshake completed231 ms
20 days agoHandshake completed2.44 s
21 days agoHandshake completed201 ms
22 days agoHandshake completed2.82 s

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