Remote MCP · Endpoint

run.onvibe/onvibe MCP server

Yes, as of 3 hours ago: the connection was refused or dropped.

DownLast checked 3 hours 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
5.6% from 18 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.
Website
https://onvibe.run/
Repository
https://github.com/ceritium/onvibe
Listing
From the official MCP registry (active).
Recent checks of run.onvibe/onvibe
CheckedResultHandshake
3 hours agoFailed - the connection was refused or dropped—
1 day agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
3 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—
6 days agoFailed - the connection was refused or dropped—
8 days agoFailed - the connection was refused or dropped—
11 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
16 days agoFailed - the connection was refused or dropped—
18 days agoFailed - the connection was refused or dropped—
20 days agoFailed - the connection was refused or dropped—
22 days agoFailed - the connection was refused or dropped—
24 days agoFailed - the connection was refused or dropped—
26 days agoFailed - the connection was refused or dropped—
27 days agoFailed - the connection was refused or dropped—
29 days agoHandshake completed123 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.