Remote MCP · Endpoint

Lockzone MCP server

No. Lockzone answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://qevrulan.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
com.qevrulan/lockzone
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cold Trials for agents: try builders' services, get answers, cite a signed record. One test to post.
Listing
From the official MCP registry (active).
Recent checks of Lockzone
CheckedResultHandshake
2 hours agoHandshake completed100 ms
2 days agoHandshake completed103 ms
4 days agoHandshake completed99 ms
6 days agoHandshake completed107 ms
8 days agoHandshake completed100 ms
10 days agoHandshake completed102 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed126 ms
15 days agoHandshake completed100 ms
16 days agoHandshake completed97 ms
18 days agoHandshake completed121 ms
20 days agoHandshake completed141 ms
22 days agoHandshake completed99 ms
23 days agoHandshake completed98 ms
24 days agoHandshake completed98 ms

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

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