Remote MCP · Endpoint

BugEzy MCP server

No. BugEzy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bugezy.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.bugezy/bugezy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.
Listing
From the official MCP registry (active).
Recent checks of BugEzy
CheckedResultHandshake
1 hour agoHandshake completed293 ms
2 days agoHandshake completed203 ms
4 days agoHandshake completed283 ms
5 days agoHandshake completed464 ms
7 days agoHandshake completed36 ms
8 days agoHandshake completed397 ms
9 days agoHandshake completed385 ms
12 days agoHandshake completed195 ms
13 days agoHandshake completed353 ms
15 days agoHandshake completed212 ms
16 days agoHandshake completed212 ms
18 days agoHandshake completed35 ms
19 days agoHandshake completed196 ms
20 days agoHandshake completed203 ms
20 days agoHandshake completed197 ms
21 days agoHandshake completed267 ms
22 days agoHandshake completed244 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 BugEzy and makes no claim about it beyond what these checks measured.