Remote MCP · Endpoint

Neblla MCP server

No. Neblla answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://neblla.com/mcp

The last check completed an MCP handshake.

Registry name
com.neblla/neblla
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
108 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Build and publish multiplayer apps and games on Neblla: scaffold, edit files, ship to the gallery.
Listing
From the official MCP registry (active).
Recent checks of Neblla
CheckedResultHandshake
1 hour agoHandshake completed194 ms
2 days agoHandshake completed161 ms
4 days agoHandshake completed146 ms
5 days agoHandshake completed168 ms
7 days agoHandshake completed192 ms
8 days agoHandshake completed300 ms
9 days agoHandshake completed144 ms
12 days agoHandshake completed141 ms
13 days agoHandshake completed162 ms
15 days agoHandshake completed143 ms
16 days agoHandshake completed169 ms
17 days agoHandshake completed138 ms
18 days agoHandshake completed304 ms
19 days agoHandshake completed308 ms
20 days agoHandshake completed140 ms
21 days agoHandshake completed168 ms
22 days agoHandshake completed152 ms

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