Remote MCP · Endpoint

run.onvibe/onvibe MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://onvibe.run/mcp

The last check failed: the connection was refused or dropped.

Registry name
run.onvibe/onvibe
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
70.6% from 17 checks
Described by its publisher as
Talk to Claude and get a live web app deployed to a real URL, with Postgres, storage and cron.
Listing
From the official MCP registry (active).
Recent checks of run.onvibe/onvibe
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the connection was refused or dropped—
5 days agoFailed - the connection was refused or dropped—
7 days agoFailed - the connection was refused or dropped—
8 days agoHandshake completed123 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed110 ms
13 days agoHandshake completed123 ms
15 days agoHandshake completed115 ms
17 days agoHandshake completed133 ms
18 days agoHandshake completed108 ms
19 days agoHandshake completed116 ms
20 days agoHandshake completed118 ms
21 days agoHandshake completed117 ms
21 days agoHandshake completed131 ms
23 days agoHandshake completed116 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 run.onvibe/onvibe and makes no claim about it beyond what these checks measured.