Remote MCP · Endpoint

Bursia MCP Visitor Gateway Canary MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.soyeladice-svg/bursia-canary
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
73.7% from 19 checks
Described by its publisher as
Bursia MCP canary: 8 compatibility tools + 7 visitor tools with verified operator grants.
Website
https://burs-ia.com/
Repository
https://github.com/soyeladice-svg/-burs-ia-interop-lab.
Listing
From the official MCP registry (deprecated).
Recent checks of Bursia MCP Visitor Gateway Canary
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoHandshake completed203 ms
6 days agoHandshake completed201 ms
8 days agoHandshake completed228 ms
11 days agoHandshake completed164 ms
13 days agoHandshake completed241 ms
15 days agoHandshake completed208 ms
18 days agoHandshake completed207 ms
20 days agoHandshake completed297 ms
22 days agoHandshake completed254 ms
24 days agoHandshake completed201 ms
26 days agoHandshake completed199 ms
27 days agoHandshake completed195 ms
28 days agoHandshake completed233 ms
29 days agoHandshake completed870 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 24 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.