Remote MCP · Endpoint

짓닷 자재 찾기 MCP server

No. 짓닷 자재 찾기 answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://jitdot.com/mcp

The last check completed an MCP handshake.

Registry name
com.jitdot/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.36 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
짓닷(jitdot.com)에 공개된 타일 · 마루 · LVT 등 인테리어 마감재를 규격 · 재질 · 마감으로 찾는 읽기 전용 카탈로그
Listing
From the official MCP registry (active).
Recent checks of 짓닷 자재 찾기
CheckedResultHandshake
19 minutes agoHandshake completed1.36 s
3 days agoHandshake completed921 ms
14 days agoHandshake completed1.12 s
14 days agoHandshake completed1.04 s
15 days agoHandshake completed866 ms
16 days agoHandshake completed1.08 s
18 days agoHandshake completed675 ms
18 days agoHandshake completed1.10 s
19 days agoHandshake completed839 ms
21 days agoHandshake completed926 ms
22 days agoHandshake completed938 ms
25 days agoHandshake completed923 ms
27 days agoHandshake completed841 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 짓닷 자재 찾기 and makes no claim about it beyond what these checks measured.