Remote MCP · Endpoint
IBTCC 공기업 경쟁률 조회 MCP server
No. IBTCC 공기업 경쟁률 조회 answered an MCP handshake 4 hours ago.
UpLast checked 4 hours ago
Server URL
https://ibtcc.kr/api/mcp
The last check completed an MCP handshake.
- Registry name
- kr.ibtcc/competition-ratio
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 146 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다.
- Repository
- https://github.com/jojunho74/hometest
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 4 hours ago | Handshake completed | 146 ms |
| 15 hours ago | Handshake completed | 79 ms |
| 1 day ago | Handshake completed | 203 ms |
| 2 days ago | Handshake completed | 57 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 IBTCC 공기업 경쟁률 조회 and makes no claim about it beyond what these checks measured.