Remote MCP · Endpoint

Vibe Shipped MCP server

No. Vibe Shipped answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://vibeshipped.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.sorindecu/vibeshipped
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
143 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find the right AI tool or MCP connector for a task; sourced directory of real AI-built apps.
Listing
From the official MCP registry (active).
Recent checks of Vibe Shipped
CheckedResultHandshake
5 hours agoHandshake completed143 ms
9 days agoHandshake completed196 ms
10 days agoHandshake completed188 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed133 ms
14 days agoHandshake completed104 ms
15 days agoHandshake completed121 ms
17 days agoHandshake completed178 ms
19 days agoHandshake completed346 ms
21 days agoHandshake completed218 ms
24 days agoHandshake completed196 ms
26 days agoHandshake completed223 ms
28 days agoHandshake completed85 ms

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

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