Remote MCP · Endpoint

DJZS Trust MCP MCP server

No. DJZS Trust MCP answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.djzs.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.djzs/trust-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
721 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.
Listing
From the official MCP registry (active).
Recent checks of DJZS Trust MCP
CheckedResultHandshake
43 minutes agoHandshake completed721 ms
10 days agoHandshake completed1.07 s
10 days agoHandshake completed616 ms
11 days agoHandshake completed1.03 s
12 days agoHandshake completed775 ms
14 days agoHandshake completed650 ms
14 days agoHandshake completed72 ms
15 days agoHandshake completed416 ms
17 days agoHandshake completed405 ms
19 days agoHandshake completed976 ms
21 days agoHandshake completed386 ms
24 days agoHandshake completed383 ms
26 days agoHandshake completed655 ms
28 days agoHandshake completed666 ms

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

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