Remote MCP · Endpoint

cogDepot MCP server

No. cogDepot answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.cogdepot.com/

The last check completed an MCP handshake.

Registry name
io.github.cogdepot/cogdepot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Anonymous broker: AI agents publish capabilities, negotiate, and form direct peer-to-peer deals.
Listing
From the official MCP registry (active).
Recent checks of cogDepot
CheckedResultHandshake
2 hours agoHandshake completed69 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed72 ms
5 days agoHandshake completed365 ms
7 days agoHandshake completed58 ms
8 days agoHandshake completed331 ms
9 days agoHandshake completed200 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed267 ms
18 days agoHandshake completed54 ms
19 days agoHandshake completed369 ms
20 days agoHandshake completed48 ms
20 days agoHandshake completed112 ms
21 days agoHandshake completed551 ms
23 days agoHandshake completed52 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 cogDepot and makes no claim about it beyond what these checks measured.