Remote MCP · Endpoint

io.github.Olum289/agentlock MCP server

No. io.github.Olum289/agentlock answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://app.agentlock.net/api/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
io.github.Olum289/agentlock
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
992 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Listing
From the official MCP registry (active).
Recent checks of io.github.Olum289/agentlock
CheckedResultHandshake
1 hour agoHandshake completed992 ms
1 day agoHandshake completed2.54 s
2 days agoHandshake completed2.78 s
3 days agoHandshake completed946 ms
4 days agoHandshake completed889 ms
5 days agoHandshake completed156 ms
6 days agoHandshake completed141 ms
9 days agoHandshake completed109 ms
11 days agoHandshake completed202 ms
14 days agoHandshake completed215 ms
16 days agoHandshake completed1.75 s
18 days agoHandshake completed1.08 s
20 days agoHandshake completed1.57 s
22 days agoHandshake completed906 ms
24 days agoHandshake completed119 ms
26 days agoHandshake completed121 ms
27 days agoHandshake completed160 ms
29 days agoHandshake completed2.40 s

The last 18 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.github.Olum289/agentlock and makes no claim about it beyond what these checks measured.