Remote MCP · Endpoint

noback MCP server

No. noback answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://apps.noback.page/mcp

The last check completed an MCP handshake.

Registry name
app.noback/noback
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
431 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed.
Listing
From the official MCP registry (active).
Recent checks of noback
CheckedResultHandshake
20 minutes agoHandshake completed431 ms
3 days agoHandshake completed428 ms
14 days agoHandshake completed492 ms
14 days agoHandshake completed516 ms
15 days agoHandshake completed441 ms
16 days agoHandshake completed430 ms
18 days agoHandshake completed441 ms
18 days agoHandshake completed413 ms
19 days agoHandshake completed439 ms
21 days agoHandshake completed463 ms
22 days agoHandshake completed7.40 s
25 days agoHandshake completed472 ms

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

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