Remote MCP · Endpoint
Trust Boundary Systems MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://mcp.trustboundarysystems.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.trustboundarysystems/bookings
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 82.4% from 17 checks
- Described by its publisher as
- Book a strategy call with Trust Boundary Systems (blockchain, stablecoins, MPC, ZK, AI advisory).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour 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 | Handshake completed | 503 ms |
| 7 days ago | Handshake completed | 338 ms |
| 8 days ago | Handshake completed | 851 ms |
| 9 days ago | Handshake completed | 694 ms |
| 12 days ago | Handshake completed | 347 ms |
| 13 days ago | Handshake completed | 427 ms |
| 15 days ago | Handshake completed | 426 ms |
| 16 days ago | Handshake completed | 519 ms |
| 18 days ago | Handshake completed | 371 ms |
| 19 days ago | Handshake completed | 320 ms |
| 20 days ago | Handshake completed | 509 ms |
| 20 days ago | Handshake completed | 312 ms |
| 21 days ago | Handshake completed | 358 ms |
| 22 days ago | Handshake completed | 1.67 s |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Trust Boundary Systems and makes no claim about it beyond what these checks measured.