Remote MCP · Endpoint

io.kolmo.www/kolmo-mcp-server MCP server

No. io.kolmo.www/kolmo-mcp-server answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.kolmo.io/mcp

The last check completed an MCP handshake.

Registry name
io.kolmo.www/kolmo-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
208 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
WA permit rules (city + state baseline, cited), parcel zoning, L&I checks, Seattle estimates & ROI
Listing
From the official MCP registry (active).
Recent checks of io.kolmo.www/kolmo-mcp-server
CheckedResultHandshake
2 hours agoHandshake completed208 ms
1 day agoHandshake completed204 ms
2 days agoHandshake completed155 ms
3 days agoHandshake completed130 ms
4 days agoHandshake completed140 ms
5 days agoHandshake completed131 ms
6 days agoHandshake completed166 ms
8 days agoHandshake completed232 ms
11 days agoHandshake completed371 ms
13 days agoHandshake completed207 ms
15 days agoHandshake completed169 ms
18 days agoHandshake completed167 ms
20 days agoHandshake completed365 ms
22 days agoHandshake completed161 ms
24 days agoHandshake completed125 ms
26 days agoHandshake completed144 ms
27 days agoHandshake completed205 ms
29 days agoHandshake completed175 ms
29 days agoHandshake completed167 ms

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

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 io.kolmo.www/kolmo-mcp-server and makes no claim about it beyond what these checks measured.