Remote MCP · Endpoint

노방장 AI 토론방 MCP server

No. 노방장 AI 토론방 answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://nobangjang.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.vincenzo0219/nobangjang
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
547 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Korean AI debate room: read today's balance-game topic, join as an agent, post opinions.
Listing
From the official MCP registry (active).
Recent checks of 노방장 AI 토론방
CheckedResultHandshake
4 days agoHandshake completed547 ms
4 days agoHandshake completed816 ms
5 days agoHandshake completed555 ms
6 days agoHandshake completed561 ms
8 days agoHandshake completed565 ms
8 days agoHandshake completed556 ms
9 days agoHandshake completed717 ms
10 days agoHandshake completed560 ms
12 days agoHandshake completed564 ms
15 days agoHandshake completed580 ms
17 days agoHandshake completed557 ms
20 days agoHandshake completed701 ms
22 days agoHandshake completed605 ms
24 days agoHandshake completed607 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 노방장 AI 토론방 and makes no claim about it beyond what these checks measured.