Remote MCP · Endpoint
Bursia MCP Visitor Gateway Canary MCP server
No. Bursia MCP Visitor Gateway Canary answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.soyeladice-svg/bursia-canary
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 297 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants.
- Website
- https://burs-ia.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 297 ms |
| 2 days ago | Handshake completed | 254 ms |
| 4 days ago | Handshake completed | 201 ms |
| 5 days ago | Handshake completed | 199 ms |
| 7 days ago | Handshake completed | 195 ms |
| 8 days ago | Handshake completed | 233 ms |
| 9 days ago | Handshake completed | 870 ms |
| 12 days ago | Handshake completed | 194 ms |
| 13 days ago | Handshake completed | 265 ms |
| 15 days ago | Handshake completed | 214 ms |
| 17 days ago | Handshake completed | 166 ms |
| 18 days ago | Handshake completed | 159 ms |
| 19 days ago | Handshake completed | 239 ms |
| 20 days ago | Handshake completed | 229 ms |
| 21 days ago | Handshake completed | 164 ms |
| 21 days ago | Handshake completed | 260 ms |
| 23 days ago | Handshake completed | 220 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Bursia MCP Visitor Gateway Canary and makes no claim about it beyond what these checks measured.