Remote MCP · Endpoint

Complyzard MCP server

No. Complyzard answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://complyzard.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.InstaBlick/complyzard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
385 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
The Compliance Knowledge Marketplace. Accessible to people and AI. Find it on Complyzard.
Listing
From the official MCP registry (active).
Recent checks of Complyzard
CheckedResultHandshake
1 hour agoHandshake completed385 ms
1 day agoHandshake completed272 ms
2 days agoHandshake completed375 ms
3 days agoHandshake completed902 ms
4 days agoHandshake completed245 ms
5 days agoHandshake completed303 ms
6 days agoHandshake completed263 ms
9 days agoHandshake completed248 ms
11 days agoHandshake completed273 ms
14 days agoHandshake completed243 ms
16 days agoHandshake completed260 ms
18 days agoHandshake completed930 ms
20 days agoHandshake completed505 ms
22 days agoHandshake completed957 ms
24 days agoHandshake completed1.01 s

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