Remote MCP · Endpoint

Assistant Hub MCP server

No. Assistant Hub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rmassistanthub.io/mcp

The last check completed an MCP handshake.

Registry name
io.rmassistanthub/assistant-hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
318 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ranked crypto setups with a graded track record, and trading skills with public records.
Listing
From the official MCP registry (active).
Recent checks of Assistant Hub
CheckedResultHandshake
1 hour agoHandshake completed318 ms
2 days agoHandshake completed342 ms
5 days agoHandshake completed350 ms
7 days agoHandshake completed578 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed1.15 s
13 days agoHandshake completed287 ms
15 days agoHandshake completed305 ms
17 days agoHandshake completed292 ms
19 days agoHandshake completed333 ms
20 days agoHandshake completed292 ms
22 days agoHandshake completed472 ms
23 days agoHandshake completed1.69 s
25 days agoHandshake completed314 ms

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

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