MCP Test Runner MCP server

by LovRanRan·io.github.LovRanRan/mcp-test-runner·v0.1.0

No reviews yet

Local test execution and coverage summaries for onboarding agents.

B82/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B82/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed MCP Test Runner yet.

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

MCP Test Runner tools (6, 3 write)

write = sends, deletes, buys or posts

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

get_coverage_summary
health
parse_test_output
run_jestwrite action
run_pytestwrite action
run_single_testwrite action

Public scan report

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

no findings

Code scan12 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 105 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.Rubric Appeal a finding JSON

How MCP Test Runner 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: 50%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 3 read · 3 run or deploy

Install MCP Test Runner in Claude Code, Cursor or VS Code

claude mcp add mcp-test-runner -- uvx lovranran-mcp-test-runner

Add to Cursor

What the publisher says

From the MCP Test Runner repository's README, as published. We do not edit it. Read it on GitHub

mcp-test-runner

MCP server for deterministic local test execution and normalized test result reporting.

mcp-test-runner is the verification layer for codebase onboarding agents. It exposes focused MCP tools for running pytest and Jest, parsing test output, and summarizing coverage so downstream agents can mark claims as verified, unverified, or contradicted by real execution.

Codebase Onboarding Stack

mcp-test-runner is the verification layer in a three-server MCP tool stack for Project 6 wayfinder, a codebase onboarding agent.

mcp-repo-mapper maps repository structure, languages, entry points, framework evidence, and Python dependency edges.
mcp-ast-explorer provides symbol-grounded Python definition, signature, reference, call-chain, and class-hierarchy lookups.
mcp-test-runner runs local pytest/Jest checks and coverage summaries so agent claims can be verified against execution.

In wayfinder, this server turns high-risk code understanding claims into verified, unverified, or contradicted evidence from real test execution.

Status

This repository is a Python-first v1 MCP test runner. It supports bounded pytest execution, Jest command execution, single-test targeting, pytest coverage summaries, and normalized pytest/Jest JSON parsing.

The server does not use an LLM. Test results come from subprocess execution and structured parser output.

Tools

Supported Scope

Python 3.11+ package.
FastMCP 2.x server.
pytest execution with JSON report output via pytest-json-report.
Jest command execution via npx jest --json --outputFile.
pytest and Jest JSON normalization into one TestRunResult schema.
Single pytest node id execution and Jest test-name targeting.
pytest-cov coverage summary from .coverage.json.
Subprocess timeout plus POSIX resource.setrlimit CPU / memory caps.

Current Limitations

v1 does not use Docker. It uses cwd validation, subprocess timeouts, and POSIX resource limits.
Resource limits require a POSIX platform that supports resource.setrlimit.
Jest execution expects Node.js plus project-local or npx-resolvable Jest.
Jest single-test targeting uses --testNamePattern; it does not parse Jest file-specific node ids.
Coverage summary is pytest-only in v1.
Tools return raw command output for execution; call parsetestoutput to normalize framework JSON.

Local Development

Install dependencies:

uv sync --extra dev

The PyPI distribution name is lovranran-mcp-test-runner because mcp-test-runner is already taken on PyPI. The installed console script remains mcp-test-runner.

Run the MCP server:

uv run mcp-test-runner

Run verification:

uv run ruff check .
uv run mypy
uv run pytest

License

MIT

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

MCP Test Runner: common questions

Is MCP Test Runner MCP server safe?: Mostly: it is graded B (82/100). Read the MCP Test Runner safety report
How do I install MCP Test Runner?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does MCP Test Runner need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MCP Test Runner maintained?: The last commit was 142 days ago (2026-06-15). The latest release is v0.1.0.
How does MCP Test Runner 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 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.