Remote MCP · Endpoint

MONO Social MCP server

No. MONO Social answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mono.juno.ventures/mcp

The last check completed an MCP handshake.

Registry name
io.github.junoventures/mono-juno-ventures
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
73 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MONO Social — directory of places, events, and listings.
Listing
From the official MCP registry (active).
Recent checks of MONO Social
CheckedResultHandshake
1 hour agoHandshake completed73 ms
2 days agoHandshake completed69 ms
4 days agoHandshake completed140 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed91 ms
9 days agoHandshake completed73 ms
12 days agoHandshake completed633 ms
13 days agoHandshake completed129 ms
15 days agoHandshake completed1.07 s
17 days agoHandshake completed138 ms
18 days agoHandshake completed80 ms
19 days agoHandshake completed227 ms
20 days agoHandshake completed77 ms
20 days agoHandshake completed102 ms
21 days agoHandshake completed104 ms
23 days agoHandshake completed619 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 MONO Social and makes no claim about it beyond what these checks measured.