Remote MCP · Endpoint

Hologram Model Hub MCP server

No. Hologram Model Hub answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://hub.uor.foundation/mcp

The last check completed an MCP handshake.

Registry name
foundation.uor.hub/model-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.07 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Find open models and get download links with the SHA-256 each file must have.
Listing
From the official MCP registry (active).
Recent checks of Hologram Model Hub
CheckedResultHandshake
2 hours agoHandshake completed1.07 s
2 days agoHandshake completed110 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed76 ms
7 days agoHandshake completed457 ms
8 days agoHandshake completed231 ms
9 days agoHandshake completed145 ms
12 days agoHandshake completed165 ms
13 days agoHandshake completed77 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed106 ms
18 days agoHandshake completed132 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed74 ms
20 days agoHandshake completed65 ms
21 days agoHandshake completed57 ms

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

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