Remote MCP · Endpoint

VibeCodePicks MCP server

No. VibeCodePicks answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vibecodepicks.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.suanrongbaicai/vibecodepicks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
30 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pick AI coding tools by goal: community-sentiment rankings, pricing, free tiers, alternatives.
Listing
From the official MCP registry (active).
Recent checks of VibeCodePicks
CheckedResultHandshake
1 hour agoHandshake completed86 ms
8 days agoHandshake completed683 ms
9 days agoHandshake completed159 ms
11 days agoHandshake completed120 ms
12 days agoHandshake completed83 ms
13 days agoHandshake completed744 ms
14 days agoHandshake completed693 ms
14 days agoHandshake completed665 ms
16 days agoHandshake completed173 ms
19 days agoHandshake completed705 ms
21 days agoHandshake completed153 ms
24 days agoHandshake completed702 ms
26 days agoHandshake completed87 ms
28 days agoHandshake completed472 ms

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

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