Remote MCP · Endpoint

BOIM Korea Vendor Directory MCP server

No. BOIM Korea Vendor Directory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://boim.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.boim/vendors
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
430 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
BOIM(보임): Korean businesses (2.7M, all industries), public-procurement vendors and live public bids.
Listing
From the official MCP registry (active).
Recent checks of BOIM Korea Vendor Directory
CheckedResultHandshake
1 hour agoHandshake completed430 ms
2 days agoHandshake completed280 ms
5 days agoHandshake completed313 ms
7 days agoHandshake completed241 ms
9 days agoHandshake completed399 ms
11 days agoHandshake completed430 ms
13 days agoHandshake completed299 ms
15 days agoHandshake completed349 ms
17 days agoHandshake completed291 ms
18 days agoHandshake completed254 ms
20 days agoHandshake completed274 ms
21 days agoHandshake completed736 ms
23 days agoHandshake completed932 ms
25 days agoHandshake completed1.04 s

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 BOIM Korea Vendor Directory and makes no claim about it beyond what these checks measured.