Remote MCP · Endpoint

独行录 / opcmenu MCP server

No. 独行录 / opcmenu answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.opcmenu.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.yzlee/opcmenu
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
772 ms
Tools exposed
463 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find founders, collaboration opportunities and events; manage authorized signups and messages.
Listing
From the official MCP registry (active).
Recent checks of 独行录 / opcmenu
CheckedResultHandshake
1 hour agoHandshake completed772 ms
9 days agoHandshake completed1.83 s
10 days agoHandshake completed1.67 s
11 days agoHandshake completed2.09 s
12 days agoHandshake completed764 ms
14 days agoHandshake completed823 ms
14 days agoHandshake completed744 ms
15 days agoHandshake completed837 ms
17 days agoHandshake completed1.52 s
19 days agoHandshake completed755 ms
21 days agoHandshake completed712 ms
24 days agoHandshake completed754 ms
26 days agoHandshake completed874 ms
28 days agoHandshake completed732 ms

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

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 独行录 / opcmenu and makes no claim about it beyond what these checks measured.