Remote MCP · Endpoint

CliDeck MCP — Network Knowledge MCP server

No. CliDeck MCP — Network Knowledge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.clideck.com/mcp

The last check completed an MCP handshake.

Registry name
com.clideck/network-knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
221 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Free verified network knowledge for AI agents: deterministic answers, honest unknowns.
Listing
From the official MCP registry (active).
Recent checks of CliDeck MCP — Network Knowledge
CheckedResultHandshake
1 hour agoHandshake completed221 ms
19 hours agoHandshake completed158 ms
2 days agoHandshake completed170 ms
3 days agoHandshake completed177 ms
4 days agoHandshake completed168 ms
5 days agoHandshake completed186 ms
6 days agoHandshake completed187 ms
8 days agoHandshake completed765 ms
10 days agoHandshake completed144 ms
13 days agoHandshake completed518 ms
15 days agoHandshake completed146 ms
17 days agoHandshake completed138 ms
19 days agoHandshake completed223 ms
21 days agoHandshake completed204 ms
23 days agoHandshake completed137 ms
25 days agoHandshake completed192 ms
27 days agoHandshake completed165 ms
28 days agoHandshake completed195 ms
29 days agoHandshake completed641 ms

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

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 CliDeck MCP — Network Knowledge and makes no claim about it beyond what these checks measured.