Remote MCP · Endpoint

ai.colaunched/public MCP server

No. ai.colaunched/public answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.colaunched.ai/public

The last check completed an MCP handshake.

Registry name
ai.colaunched/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
99 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Business ideas from real public demand, scored with dated evidence. No account needed.
Listing
From the official MCP registry (active).
Recent checks of ai.colaunched/public
CheckedResultHandshake
5 hours agoHandshake completed99 ms
9 days agoHandshake completed125 ms
10 days agoHandshake completed156 ms
11 days agoHandshake completed196 ms
12 days agoHandshake completed128 ms
14 days agoHandshake completed118 ms
14 days agoHandshake completed115 ms
15 days agoHandshake completed57 ms
17 days agoHandshake completed113 ms
19 days agoHandshake completed107 ms
21 days agoHandshake completed133 ms
24 days agoHandshake completed145 ms
26 days agoHandshake completed109 ms
28 days agoHandshake completed119 ms

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

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