Remote MCP · Endpoint

Hilo Studio MCP server

No. Hilo Studio answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://hilostudiolab.com/mcp

The last check completed an MCP handshake.

Registry name
com.hilostudiolab/studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
208 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Madrid studio for branding and interactive 3D web: services, prices, work, Lab demos, quotes.
Listing
From the official MCP registry (active).
Recent checks of Hilo Studio
CheckedResultHandshake
2 hours agoHandshake completed208 ms
1 day agoHandshake completed73 ms
3 days agoHandshake completed61 ms
3 days agoHandshake completed206 ms
4 days agoHandshake completed697 ms
5 days agoHandshake completed75 ms
7 days agoHandshake completed66 ms
10 days agoHandshake completed61 ms
12 days agoHandshake completed82 ms
15 days agoHandshake completed91 ms
17 days agoHandshake completed1.01 s
19 days agoHandshake completed1.06 s
21 days agoHandshake completed89 ms
23 days agoHandshake completed99 ms
25 days agoHandshake completed378 ms

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

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