Remote MCP · Endpoint
kubik-tools MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://mcp.kubik.tools/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.markopolovic/kubik-tools
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 58.8% from 17 checks
- Described by its publisher as
- Freight calculators (weight, metres, vehicle fit) and authenticated team packing-library tools.
- Website
- https://kubik.tools/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Handshake completed | 670 ms |
| 13 days ago | Handshake completed | 660 ms |
| 15 days ago | Handshake completed | 612 ms |
| 17 days ago | Handshake completed | 530 ms |
| 18 days ago | Handshake completed | 631 ms |
| 19 days ago | Handshake completed | 723 ms |
| 20 days ago | Handshake completed | 444 ms |
| 20 days ago | Handshake completed | 451 ms |
| 21 days ago | Handshake completed | 791 ms |
| 23 days ago | Handshake completed | 567 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 17.
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 kubik-tools and makes no claim about it beyond what these checks measured.