BugEzy MCP server

• Registry namedev.bugezy/bugezyverified in the MCP registry

The registry name sits under bugezy.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools14
• Server calls itselfBugEzy
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 42 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer268 ms
• Space in an agent's context≈ 1,184 tokensthe definitions of all its tools (14), which an agent carries on every turn
• Tool definitionsC · 73 of 100
• Typed results0 of 14 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 9 of 14
• Not saying whether it only reads or can destroy: 14 of 14

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_reports

  列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and session_token.

• get_report_overview

  取得報告概覽（metadata + 各筆數 + AI Bug 導航摘要，不含原始資料）。Report overview with AI bug summary.

• get_console_logs

  取得 Console 記錄（warn/error）。Console logs.

• get_network_errors

  取得 Network 錯誤（4xx/5xx）。Network errors.

• get_voice_transcript

  取得開發者語音描述（中文轉錄）。Developer voice transcript.

• get_page_info

  取得頁面資訊（URL/標題/瀏覽器/解析度）。Page info.

• get_rrweb_summary

  DOM 軌跡摘要（事件數/時長/類型分布，不回完整資料）。rrweb summary.

• get_rrweb_events

  取得完整 DOM 事件（⚠ 資料量大）。Full rrweb events.

• get_live_errors

  取得某使用者當前頁面的即時 Console/Network 錯誤（需 user_email + session_token 驗證身分）。Live console/network errors — requires user_email and session_token.

• get_terminal_logs

  取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature.

• get_usage_stats

  取得當月的 MCP 使用量統計（呼叫次數、token 消耗、省了多少）。Monthly MCP usage stats.

• get_usage_quota

  查詢目前方案與本月剩餘用量（錄製 / 回溯 / MCP 讀取）。需 user_email + session_token 驗證身分。查詢不會消耗額度。Check your plan and remaining monthly quota — requires user_email and session_token. Checking does not consume quota.

• get_screenshots

  高畫質 AI 分析：取得報告截圖圖片（視覺 Bug 用）。⚠ 圖片消耗較高 Token（每張 ~3,000-8,000），建議只在需要看畫面時使用。Report screenshots.

• get_timeline

  取得一份報告的完整時間軸（時序麵包屑）。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線，AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡（省去逐一呼叫 console/network/voice 各 tool）。Full report timeline.