Coverage intelligence online

Code coverage for AI coding agents. Exactly what to test next.

9to5 turns every coverage upload into exact uncovered changed lines, baselines, and regressions your agent can query through read-only MCP—then verifies the result in GitHub.

Install GitHub App Explore MCP docs

No credit card Free while in preview Already connected? Sign in

acme / payments · pull request #284

Live

Coverage signal

Project

91.8%

Patch

82.4%

Targets

03

Agent activity

Uncovered changed lines

read only
$

get_uncovered_changed_lines

owner: acme · repo: payments · pr: 284

lib/billing.ex 84–87
lib/checkout.ex 112–113

GitHub check synced

2 seconds ago

verified

Remote MCP

Read-only agent context

GitHub native

Checks and PR comments

Exact targets

Paths, lines, and hit states

CI compatible

LCOV · Cobertura · JaCoCo

MCP clients / Codex · Claude · any MCP-compatible coding agent

Coverage guides JavaScript & TypeScript Python Java Swift PHP Go coverage

One signal · two audiences

Coverage data that knows what happens next.

Percentages tell you risk exists. 9to5 provides the coordinates to resolve it, with a workflow designed for agents and reviewers alike.

Target resolution

Give agents coordinates, not another dashboard score.

Query exact changed paths, contiguous uncovered ranges, nearby hit states, and the baseline behind every result.

PATH
lib/billing.ex
RANGE
84–87
STATE
UNCOVERED

Baseline intelligence

Know exactly what got better, or worse.

Compare project, file, and line states against the matching base branch run. Regressions surface without static-threshold noise.

Human review

The agent gets context. Reviewers get clarity.

Keep project and patch checks, pull request comments, and drill-down run pages in the GitHub workflow your team already trusts.

9to5 coverage — Patch coverage

Check completed in 18s

PASS

Read-only by design

Your source stays in the checkout.

MCP exposes authorized coverage metadata—never repository source. The coding agent reads code locally and uses 9to5 only to find and verify the right targets.

Closed-loop workflow

From CI signal to verified change.

Every step has a clear owner. CI produces coverage, 9to5 resolves context, your agent works locally, and GitHub records the result.

View integration guides
  1. 01

    Upload

    Send LCOV, Cobertura, or JaCoCo from your existing CI run.

  2. 02

    Query

    Resolve the PR baseline and exact uncovered changed ranges.

  3. 03

    Target

    Let the coding agent inspect source and write focused tests locally.

  4. 04

    Verify

    Upload again and confirm the patch improved with GitHub checks.

Ready for the next pull request

Stop sending agents a score. Give them the next move.

Connect GitHub, upload your first coverage report, and turn every gap into actionable context.

Install GitHub App Explore MCP docs