Remote MCP · Endpoint
Tjaz MCP server
No. Tjaz answered an MCP handshake 20 minutes ago.
UpLast checked 20 minutes ago
Server URL
https://tjaz.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.tjaz/quiz
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 343 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Make, find and share multiple-choice quizzes that people play on tjaz.com, alone or together
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 minutes ago | Handshake completed | 343 ms |
| 3 days ago | Handshake completed | 248 ms |
| 14 days ago | Handshake completed | 254 ms |
| 14 days ago | Handshake completed | 259 ms |
| 15 days ago | Handshake completed | 396 ms |
| 16 days ago | Handshake completed | 260 ms |
| 18 days ago | Handshake completed | 333 ms |
| 18 days ago | Handshake completed | 253 ms |
| 19 days ago | Handshake completed | 259 ms |
| 21 days ago | Handshake completed | 259 ms |
| 23 days ago | Handshake completed | 320 ms |
| 25 days ago | Handshake completed | 255 ms |
| 28 days ago | Handshake completed | 248 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Tjaz and makes no claim about it beyond what these checks measured.