Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is BugEzy free to use?

Yes — the hub reached it with no key and no payment.

What tools does BugEzy have?

14 tools: get_voice_transcript, get_terminal_logs, get_console_logs, get_page_info, get_live_errors, get_network_errors, get_rrweb_events, get_screenshots, ….

Is BugEzy safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 2h ago

BugEzy

https://bugezy.dev

Registry code: a8256efea6ce5078

api record

Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.

from a public catalogue that lists it, not from the operator

endpoint: https://bugezy.dev/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is BugEzy live?: Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is BugEzy free to use?: Yes — the hub reached it with no key and no payment.
What tools does BugEzy have?: 14 tools: get_voice_transcript, get_terminal_logs, get_console_logs, get_page_info, get_live_errors, get_network_errors, get_rrweb_events, get_screenshots, ….
Is BugEzy safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.7%

90 days 99.8%· all time 99.8%

latency

388ms

last good check

priced tools

of 14 tools

_ answered our checks, 90 days 421 checks · signed record

2026-10-20 19:26 degraded → live
2026-10-20 18:10 live → degraded· timeout after 20000ms
2026-10-12 10:30 degraded → live
2026-09-26 19:58 unknown → live

_ what it is for

topic: developer tools testing & qa
used for: read a bug report's console and network errors
get a bug report timeline
view bug report screenshots
get live errors from a user's page
takes → gives: text → data, images, text
tools: 14 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 14 tools

3 open 11 never probed 3 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_usage_quota reads open 10h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "user_email": {
      "type": "string",
      "description": "使用者 email。未提供則無法查詢（安全預設）。"
    },
    "session_token": {
      "type": "string",
      "description": "BugEzy session token（MCP URL 已帶 ?token= 則不需提供）。"
    }
  }
}

arguments 14 lines

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

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

list_reports reads open 10h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "url": {
      "type": "string"
    },
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1
    },
    "user_email": {
      "type": "string",
      "description": "使用者 email；只回傳該 email 的報告。未提供則不回任何報告（安全預設）。"
    },
    "session_token": {
      "type": "string",
      "description": "BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。"
    }
  }
}

arguments 22 lines

get_voice_transcript reads unknown 13h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_terminal_logs reads unknown 2h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "user_email"
  ],
  "properties": {
    "user_email": {
      "type": "string",
      "description": "你的 BugEzy email（只讀你自己的終端機日誌）"
    },
    "session_token": {
      "type": "string",
      "description": "BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。"
    }
  }
}

arguments 17 lines

get_console_logs reads unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_page_info reads unknown 18h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_live_errors reads unknown 2h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "user_email"
  ],
  "properties": {
    "user_email": {
      "type": "string",
      "description": "你的 BugEzy email（只讀你自己的即時錯誤）"
    },
    "session_token": {
      "type": "string",
      "description": "BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。"
    }
  }
}

arguments 17 lines

get_network_errors reads unknown 2h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_rrweb_events reads unknown 13h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

get_screenshots reads unknown 7h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    },
    "include_images": {
      "type": "boolean",
      "description": "開啟高畫質 AI 分析（預設 false，只回 metadata 省 Token）"
    }
  }
}

arguments 16 lines

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

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "report_id" ], "properties": { "report_id": { "type": "string" } } }
arguments 12 lines
get_timeline reads unknown 18h ago
取得一份報告的完整時間軸（時序麵包屑）。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線，AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡（省去逐一呼叫 console/network/voice 各 tool）。Full report timeline.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "report_id" ], "properties": { "report_id": { "type": "string", "description": "報告 ID" } } }
arguments 13 lines

get_rrweb_summary reads unknown 13h ago

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

arguments 12 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a8256efea6ce5078.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a8256efea6ce5078/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/a8256efea6ce5078/badge.svg)](https://brick.blue/agent/a8256efea6ce5078?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.