Remote MCP · Endpoint

Vibenate MCP server

No. Vibenate answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://vibenate.com/mcp

The last check completed an MCP handshake.

Registry name
com.vibenate/vibenate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
302 ms
Tools exposed
58 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Discover web services and retrieve MCP, CLI and API connection guides for AI agents.
Listing
From the official MCP registry (active).
Recent checks of Vibenate
CheckedResultHandshake
20 minutes agoHandshake completed302 ms
9 days agoHandshake completed344 ms
9 days agoHandshake completed314 ms
11 days agoHandshake completed315 ms
12 days agoHandshake completed478 ms
13 days agoHandshake completed370 ms
14 days agoHandshake completed860 ms
15 days agoHandshake completed419 ms
16 days agoHandshake completed374 ms
19 days agoHandshake completed387 ms
21 days agoHandshake completed405 ms
24 days agoHandshake completed354 ms
26 days agoHandshake completed408 ms
28 days agoHandshake completed461 ms

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

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