Remote MCP · Endpoint
SBGrid3.0 MCP MCP server
No. SBGrid3.0 MCP answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://softbowl.co.kr/mcp/sbgrid3.do
The last check completed an MCP handshake.
- Registry name
- kr.co.softbowl/sbgrid3
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 772 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Softbowl SBGrid3.0 데이터 그리드(grid)의 공식 API 문서를 검색해, AI가 정확한 그리드 코드를 생성하도록 돕습니다.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 772 ms |
| 15 hours ago | Handshake completed | 763 ms |
| 1 day ago | Handshake completed | 767 ms |
| 2 days ago | Handshake completed | 587 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 SBGrid3.0 MCP and makes no claim about it beyond what these checks measured.