Remote MCP · Endpoint

Agentic Keychain MCP server

No. Agentic Keychain answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://agentickeychain.com/mcp

The last check completed an MCP handshake.

Registry name
com.agentickeychain/agentic-keychain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
285 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent Skill ROI Registry & Benchmarking. It sells skills for log triage and repository mapping.
Listing
From the official MCP registry (active).
Recent checks of Agentic Keychain
CheckedResultHandshake
4 hours agoHandshake completed285 ms
2 days agoHandshake completed322 ms
4 days agoHandshake completed289 ms
6 days agoHandshake completed294 ms
8 days agoHandshake completed320 ms
10 days agoHandshake completed391 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed316 ms
14 days agoHandshake completed297 ms
16 days agoHandshake completed395 ms
18 days agoHandshake completed303 ms
20 days agoHandshake completed284 ms
21 days agoHandshake completed290 ms
23 days agoHandshake completed301 ms

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

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