BugEzy
REMOTE · BUGEZY.DEV · SCANNED OCT 4
Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1002 tokens (~71/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BugEzy MCP server?
BugEzy is a hosted endpoint at https://bugezy.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bugezy.dev
claude mcp add --transport http dev-bugezy-bugezy 'https://bugezy.dev/mcp'
{
"mcpServers": {
"dev-bugezy-bugezy": {
"url": "https://bugezy.dev/mcp"
}
}
} {
"servers": {
"dev-bugezy-bugezy": {
"type": "http",
"url": "https://bugezy.dev/mcp"
}
}
} [mcp_servers.dev-bugezy-bugezy] url = "https://bugezy.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-bugezy-bugezy": {
"type": "remote",
"url": "https://bugezy.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-bugezy-bugezy --url 'https://bugezy.dev/mcp' --transport streamable-http
mcp_servers:
dev-bugezy-bugezy:
url: "https://bugezy.dev/mcp" {
"McpServers": {
"dev-bugezy-bugezy": {
"Transport": "http",
"Url": "https://bugezy.dev/mcp"
}
}
} assistant mcp add dev-bugezy-bugezy -t streamable-http -u 'https://bugezy.dev/mcp'
{
"mcpServers": {
"dev-bugezy-bugezy": {
"type": "http",
"url": "https://bugezy.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 18 Aug 26 0
- Schema quality: 875 → 1002 ▼ functional
- Tool coverage: 44% → 50% ▲ functional
- New tool “get_usage_quota” functional
- 14 Aug 26 0
- HTTPS: unverified → pass ▲ security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://bugezy.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bugezy.dev | CN=WE1,O=Google Trust Services,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5e7151777642edeb13b520714734316b |
| SANs: bugezy.dev, *.bugezy.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bugezy.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| bugezy.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bugezy.dev/mcp | Verified | 200 | |
| http (plaintext) | http://bugezy.dev/mcp | HTTPS enforced | 301 | https://bugezy.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_console_logs ~30
取得 Console 記錄（warn/error）。Console logs.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_live_errors ~104
取得某使用者當前頁面的即時 Console/Network 錯誤（需 user_email + session_token 驗證身分）。Live console/network errors — requires user_email and session_token.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | – | BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。 |
| user_email | string | yes | 你的 BugEzy email（只讀你自己的即時錯誤） |
No output schema declared.
No examples provided.
get_network_errors ~35
取得 Network 錯誤（4xx/5xx）。Network errors.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_page_info ~38
取得頁面資訊（URL/標題/瀏覽器/解析度）。Page info.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_report_overview ~51
取得報告概覽（metadata + 各筆數 + AI Bug 導航摘要，不含原始資料）。Report overview with AI bug summary.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_rrweb_events ~38
取得完整 DOM 事件（⚠ 資料量大）。Full rrweb events.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_rrweb_summary ~44
DOM 軌跡摘要（事件數/時長/類型分布，不回完整資料）。rrweb summary.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_screenshots ~101
高畫質 AI 分析：取得報告截圖圖片（視覺 Bug 用）。⚠ 圖片消耗較高 Token（每張 ~3,000-8,000），建議只在需要看畫面時使用。Report screenshots.
| Name | Type | Req | Description |
|---|---|---|---|
| include_images | boolean | – | 開啟高畫質 AI 分析（預設 false，只回 metadata 省 Token） |
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_terminal_logs ~129
取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | – | BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。 |
| user_email | string | yes | 你的 BugEzy email（只讀你自己的終端機日誌） |
No output schema declared.
No examples provided.
get_timeline ~112
取得一份報告的完整時間軸（時序麵包屑）。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線，AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡（省去逐一呼叫 console/network/voice 各 tool）。Full report timeline.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | 報告 ID |
No output schema declared.
No examples provided.
get_usage_quota ~127
查詢目前方案與本月剩餘用量（錄製 / 回溯 / MCP 讀取）。需 user_email + session_token 驗證身分。查詢不會消耗額度。Check your plan and remaining monthly quota — requires user_email and session_token. Checking does not consume quota.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | – | BugEzy session token（MCP URL 已帶 ?token= 則不需提供）。 |
| user_email | string | – | 使用者 email。未提供則無法查詢（安全預設）。 |
No output schema declared.
No examples provided.
get_usage_stats ~37
取得當月的 MCP 使用量統計（呼叫次數、token 消耗、省了多少）。Monthly MCP usage stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_voice_transcript ~35
取得開發者語音描述（中文轉錄）。Developer voice transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
list_reports ~121
列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and session_token.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| session_token | string | – | BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。 |
| url | string | – | – |
| user_email | string | – | 使用者 email；只回傳該 email 的報告。未提供則不回任何報告（安全預設）。 |
No output schema declared.
No examples provided.
What is the BugEzy MCP server?
BugEzy is an MCP server listed in the public MCP registry as dev.bugezy/bugezy. Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them. This page covers its hosted endpoint (https://bugezy.dev/mcp).
Is the BugEzy MCP server safe to use?
BugEzy scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BugEzy MCP server expose?
BugEzy exposes 14 tools: list_reports, get_report_overview, get_console_logs, get_network_errors, get_voice_transcript, and 9 more. Their descriptions and schemas cost roughly 1,002 tokens of context every time the server is loaded.
Does the BugEzy MCP server require authentication?
No. We connected to BugEzy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BugEzy MCP server still maintained?
BugEzy is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.