"Information about bug classification" matching MCP servers:

An MCP server that gives AI coding assistants QA superpowers, enabling users to report bugs by pointing, clicking, or typing while automatically capturing diagnostic data for AI-driven test-feedback-fix loops.

Enables coding agents to turn human-verified development failures into reusable bug knowledge and executable acceptance standards, then generate graded verification plans and record structured evidence for human review.

A shared, concurrency-safe ledger for LLM code audits. It enables multiple agents to collaboratively report, verify, and resolve bugs with deduplication and hallucination resistance.

Enables managing bugs and test cases in Google Sheets via Claude Code, with tools to list, search, filter failed, and update test cases.

MCP server for Zentao that reads bugs, extracts reproduction steps, and allows AI to update bug status after fixing.

Enables AI clients to reproduce reported UI issues in an isolated, policy-restricted browser context, gather sanitized evidence, distinguish observed facts from candidate causes, and produce structured reports plus reviewable Playwright regression tests.

Enables read-only, time-boxed Postgres queries with SQL validation and PII masking, supporting automated bug triage through Claude.

MCP server that converts informal issue descriptions into structured, developer-ready bug reports using Groq, with automatic classification into bug, feature request, question, or unclear. Enables agents to generate bug reports directly without the web form.

Read visual bug reports from Feedbug in your AI coding agent: screenshot, console logs, failed network requests, session replay and the DOM context of the element the tester clicked. Trace the bug to its source file, comment and resolve without leaving the editor.

Enables recurring website maintenance checks — domain registration, SSL certificates, uptime, technical SEO and accessibility — across a portfolio of client sites, using publicly available information. Results are returned as structured data and can be sorted by urgency into a client-ready report.

Local-first bug reports for coding agents: annotated screenshots, recordings and notes stored on your machine, served over MCP with the images included. Sync reports to GitHub issues when you choose.

Enables coding agents to compile supplied files, run optional focused tests, and get static findings across ten programming languages, providing a deterministic feedback loop on the code they are about to return.

Enables independent, read-only adversarial review of candidate test cases and bug findings, returning a review delta that authoring agents reconcile before writing final artifacts.

Exposes six evidence-oriented tools over stdio so MCP clients can navigate unfamiliar code, ask typed questions about repository evidence, review completed changes, and select existing tests.

Umbra is the trust layer for AI-generated code. It scores any repo 0-100 with file:line evidence (security, slop, Docker-verified build/boot, and claim receipts that catch agents lying about tests), and guards agent file writes mid-stream blocking leaked keys, alg:none JWTs, and git-hook plants before they land. Tools: scan_repo, guard_content, get_score.

MCP server providing tools to verify task completion (tests pass and changes match claim) and confirm bug reproduction before fixing.

A local MCP server exposing jev_decide for batched classification, rubric scoring, and yes/no judgments with probabilities and token usage. Configure any compatible typed-decision API with API_KEY, BASE_URL, and MODEL.

Stops your AI from re-introducing bugs, leaking provider keys, or weakening tests. Bug fixes become permanent regression guards; blocked mistakes become AI lessons the agent reads and learns from before its next edit.

Crash-test AI agents on real professional decisions. Agents take real tariff classification and patent examination cases, search reference libraries and rulebooks, submit a decision, and get an exact score with a receipt against what the professional actually decided. Most cases were decided after current models were trained.

AI-powered website feedback and visual bug reporting MCP server that lets AI coding assistants access Vynix projects, annotations, and create GitHub issues with rich debugging context.

Bug bounty platform for vibe coders. Post bugs from AI-generated code, browse bounties, apply to fix, submit solutions, and run website diagnostics from any MCP client.

Enables coding agents to drive and inspect running Shiny apps (R and Python) by setting inputs, clicking, reading outputs, and getting detailed error information.

Automated Playwright E2E test repair powered by a self-improving, governed MCP server that runs failing tests, collects failure artifacts, reasons about root causes, validates and applies fixes, and re-runs to verify.

An MCP server that turns Zod schemas into mocks, violations, and contract tests, enabling AI agents to reason about API contracts without manually crafting payloads.

MCP server for VibeCheck bug reports. Gives AI assistants direct access to screen recordings, console logs, network requests, user actions, and web vitals — right inside your editor.

Enables AI assistants to access RenderDoc capture data and assist with graphics debugging by retrieving draw calls, shader information, buffers, textures, and pipeline state.

Lets MCP clients browse bug bounty programmes, manage reports, and triage issues on BugSecure with user-approved OAuth permissions, including read-only mode.

Analyzes Playwright test results to provide structured QA insights, including test metrics, failure analysis, bug report drafts, and release-quality recommendations.

Voice-powered bug reporting MCP server with 13 tools. Captures console logs, network errors, DOM traces, and developer voice descriptions. AI reads structured reports to find and fix bugs automatically. Chrome Extension + Python CLI.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.