Remote MCP · Endpoint
DJZS Trust MCP MCP server
No. DJZS Trust MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 664 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.
- Website
- https://djzs.ai/
- Repository
- https://github.com/SIFR0-dev/djzs-AI
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 664 ms |
| 2 days ago | Handshake completed | 367 ms |
| 4 days ago | Handshake completed | 476 ms |
| 5 days ago | Handshake completed | 586 ms |
| 7 days ago | Handshake completed | 489 ms |
| 8 days ago | Handshake completed | 431 ms |
| 9 days ago | Handshake completed | 491 ms |
| 11 days ago | Handshake completed | 414 ms |
| 13 days ago | Handshake completed | 545 ms |
| 15 days ago | Handshake completed | 688 ms |
| 17 days ago | Handshake completed | 890 ms |
| 18 days ago | Handshake completed | 338 ms |
| 19 days ago | Handshake completed | 33 ms |
| 20 days ago | Handshake completed | 412 ms |
| 21 days ago | Handshake completed | 364 ms |
| 21 days ago | Handshake completed | 557 ms |
| 23 days ago | Handshake completed | 577 ms |
| 24 days ago | Handshake completed | 663 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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.