Remote MCP · Endpoint
HOTKER 핫커 | 한국 상품·휴대폰 성지 구매가 AI MCP server
No. HOTKER 핫커 | 한국 상품·휴대폰 성지 구매가 AI answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://hotker.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.hotker/hotker
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 246 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 검증된 한국 오픈마켓 핫딜과 스마트폰 성지 판매조건을 검색하고 총비용·약정 반환금·SKT·KT·LG U+ 결합할인을 계산합니다.
- Website
- https://hotker.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 246 ms |
| 1 day ago | Handshake completed | 62 ms |
| 3 days ago | Handshake completed | 347 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 HOTKER 핫커 | 한국 상품·휴대폰 성지 구매가 AI and makes no claim about it beyond what these checks measured.