Remote MCP · Endpoint

Burs-IA MCP server

No. Burs-IA answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://burs-ia.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.soyeladice-svg/burs-ia
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
12 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Public MCP for agent verification, work discovery and governed interoperability.
Listing
From the official MCP registry (active).
Recent checks of Burs-IA
CheckedResultHandshake
1 hour agoHandshake completed101 ms
2 days agoHandshake completed158 ms
5 days agoHandshake completed129 ms
7 days agoHandshake completed172 ms
9 days agoHandshake completed209 ms
11 days agoHandshake completed126 ms
13 days agoHandshake completed189 ms
15 days agoHandshake completed138 ms
17 days agoHandshake completed118 ms
19 days agoHandshake completed196 ms
20 days agoHandshake completed176 ms
21 days agoHandshake completed124 ms
22 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed202 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 14.

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 Burs-IA and makes no claim about it beyond what these checks measured.