Remote MCP · Endpoint

VibeDoctor MCP server

No. VibeDoctor answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://vibedoctor.io/mcp

The last check completed an MCP handshake.

Registry name
io.vibedoctor/vibedoctor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
155 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
Website
https://vibedoctor.io/
Listing
From the official MCP registry (active).
Recent checks of VibeDoctor
CheckedResultHandshake
5 hours agoHandshake completed155 ms
10 hours agoHandshake completed163 ms
2 days agoHandshake completed480 ms
4 days agoHandshake completed173 ms
7 days agoHandshake completed239 ms
9 days agoHandshake completed236 ms
11 days agoHandshake completed463 ms
13 days agoHandshake completed453 ms
15 days agoHandshake completed477 ms
17 days agoHandshake completed490 ms
20 days agoHandshake completed485 ms
21 days agoHandshake completed129 ms
23 days agoHandshake completed480 ms

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

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