Remote MCP · Endpoint
za.co.zaroniacalculator.api/verify MCP server
Yes, as of 1 hour ago: the TLS certificate could not be verified.
DownLast checked 1 hour ago
Server URL
https://api.zaroniacalculator.co.za/mcp
The last check failed: the TLS certificate could not be verified.
- Registry name
- za.co.zaroniacalculator.api/verify
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 78.9% from 19 checks
- Described by its publisher as
- Independent ZARONIA coupon verification for SA FRNs & money-market paper, SARB-compounded index.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the TLS certificate could not be verified | — |
| 1 day ago | Failed - the TLS certificate could not be verified | — |
| 2 days ago | Failed - the TLS certificate could not be verified | — |
| 3 days ago | Failed - the TLS certificate could not be verified | — |
| 4 days ago | Handshake completed | 952 ms |
| 5 days ago | Handshake completed | 1.12 s |
| 6 days ago | Handshake completed | 902 ms |
| 8 days ago | Handshake completed | 932 ms |
| 11 days ago | Handshake completed | 909 ms |
| 13 days ago | Handshake completed | 897 ms |
| 15 days ago | Handshake completed | 937 ms |
| 18 days ago | Handshake completed | 948 ms |
| 20 days ago | Handshake completed | 997 ms |
| 22 days ago | Handshake completed | 906 ms |
| 24 days ago | Handshake completed | 938 ms |
| 26 days ago | Handshake completed | 926 ms |
| 27 days ago | Handshake completed | 910 ms |
| 29 days ago | Handshake completed | 903 ms |
| 29 days ago | Handshake completed | 899 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 29.
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 za.co.zaroniacalculator.api/verify and makes no claim about it beyond what these checks measured.