Remote MCP · Endpoint

DEEPBOM MCP server

No. DEEPBOM answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://deepbom.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.JunHwan-Kwon/deepbom
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Browser-local and CLI static evidence for deployed AI model artifacts.
Listing
From the official MCP registry (active).
Recent checks of DEEPBOM
CheckedResultHandshake
3 hours agoHandshake completed111 ms
2 days agoHandshake completed109 ms
4 days agoHandshake completed79 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed88 ms
8 days agoHandshake completed75 ms
9 days agoHandshake completed90 ms
12 days agoHandshake completed63 ms
13 days agoHandshake completed53 ms
15 days agoHandshake completed147 ms
16 days agoHandshake completed70 ms
17 days agoHandshake completed60 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed67 ms
22 days agoHandshake completed60 ms

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

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