Remote MCP · Endpoint

Vibe Coding 中文助手 MCP server

No. Vibe Coding 中文助手 answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://n8n.xiaomeng.ink/mcp/vibe-coding-cn

The last check completed an MCP handshake.

Registry name
io.github.menghaoran214-lang/vibe-coding-cn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
639 ms
Tools exposed
3 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Read-only Chinese Vibe Coding knowledge connector for search, docs, and repo freshness.
Listing
From the official MCP registry (active).
Recent checks of Vibe Coding 中文助手
CheckedResultHandshake
2 hours agoHandshake completed639 ms
2 days agoHandshake completed1.14 s
4 days agoHandshake completed665 ms
7 days agoHandshake completed706 ms
9 days agoHandshake completed605 ms
11 days agoFailed - the request timed out—
13 days agoHandshake completed632 ms
15 days agoHandshake completed580 ms
16 days agoHandshake completed769 ms
18 days agoHandshake completed695 ms
19 days agoHandshake completed1.16 s
20 days agoHandshake completed4.58 s
23 days agoHandshake completed286 ms
24 days agoHandshake completed303 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Vibe Coding 中文助手 and makes no claim about it beyond what these checks measured.