Remote MCP · Endpoint
io.github.dth0108/bies-guardian MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://bies.io/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.dth0108/bies-guardian
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 52.9% from 17 checks
- Described by its publisher as
- Deterministic sealed verdicts on public claims and startup ideas (0-LLM claim-safety guardian).
- Website
- https://bies.io/
- 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 | Failed - the server returned an HTTP error | — |
| 13 days ago | Handshake completed | 282 ms |
| 15 days ago | Handshake completed | 290 ms |
| 17 days ago | Handshake completed | 932 ms |
| 18 days ago | Handshake completed | 319 ms |
| 19 days ago | Handshake completed | 838 ms |
| 20 days ago | Handshake completed | 273 ms |
| 20 days ago | Handshake completed | 280 ms |
| 21 days ago | Handshake completed | 805 ms |
| 23 days ago | Handshake completed | 277 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 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 io.github.dth0108/bies-guardian and makes no claim about it beyond what these checks measured.