MCP.Market

QA Radar MCP server

by MuratKus·io.github.MuratKus/qaradar·v0.3.5
No reviews yet

Tells AI agents which files to test first — churn, coverage, and test mapping as risk scores.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed QA Radar yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

QA Radar tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • qaradar_churn

    Use when the user asks which files change most often, what the hotspots are, or where regressions tend to occur.

  • qaradar_coverage_gaps

    Use when the user asks which files have low coverage, where the blind spots are, or wants to improve test coverage.

  • qaradar_healthcheck

    Use when the user wants a full quality overview or asks 'what's the health of this repo?'.

  • qaradar_pr_risk

    Use when the user asks what's risky in this PR, which changed files need review, or which of my changes lack tests.

  • qaradar_risky_modules

    Use when the user asks what to test first, which files are riskiest, or where regressions are likely.

  • qaradar_untested_files

    Use when the user asks which files have no tests, what's completely uncovered, or wants to find testing blind spots.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan18 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 112 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How QA Radar compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
21
more than 8% of 12,191 servers with a package

What its tools let an agent do: 6 read

Install QA Radar in Claude Code, Cursor or VS Code

claude mcp add qaradar -- uvx qaradar
Add to Cursor

What the publisher says

From the QA Radar repository's README, as published. We do not edit it. Read it on GitHub

QA Radar

Give your AI coding agent the quality brain it doesn't have to grow from scratch.

QA Radar analyzes your codebase and produces a structured quality health report — combining git churn, test coverage, and test-to-source mapping into risk-scored modules. It works as an MCP server for AI coding agents (Claude Code, Cursor, Windsurf) and as a standalone CLI for humans and CI pipelines.

Built for developers who want their AI agent to write targeted tests, not generic ones.

Quick Start

Claude Code — one step:

/plugin marketplace add Muratkus/qaradar
/plugin install qaradar@qaradar-marketplace

Then ask your agent: "What should I test first?"

Or run directly without installing:

uvx qaradar serve

Full install options ↓

What It Does

QA Radar answers the question every new team member (and every AI agent) asks: "What should I test first?"

It scans three signals and combines them into a per-file risk score:

The output is a ranked list of modules by risk level (critical → low), with human-readable reasons for each rating.

Why Not Just Let the Agent Do It?

A capable agent with bash access could run git log --numstat, parse coverage.xml, and glob for test files. So why an MCP server?

Install as Claude Code Plugin (Recommended)

The fastest path — one command wires up the MCP server and installs 4 slash commands. No manual config editing.

Step 0 — install uv (if you don't have it):

curl -LsSf https://astral.sh/uv/install.sh | sh
# or: pip install uv

uv launches qaradar on demand from PyPI — you don't need to pip install qaradar separately.

Step 1 — add the marketplace:

/plugin marketplace add Muratkus/qaradar

Step 2 — install:

/plugin install qaradar@qaradar-marketplace

What you get: 6 MCP tools auto-configured + 5 slash commands:

Example: after merging a big feature branch, run /qaradar:qa-check to see what regressed. Before opening a PR, run /qaradar:qa-pr-risk to see what you need to test first.

MCP Server (for AI Coding Agents)

Setup

Alternative: manual MCP config (if you prefer not to use the plugin):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

QA Radar: common questions

Is QA Radar MCP server safe?
Mostly: it is graded B (82/100). Read the QA Radar safety report
How do I install QA Radar?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does QA Radar need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is QA Radar maintained?
The last commit was 150 days ago (2026-06-07). The latest release is v0.3.5.
How does QA Radar compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.