Universal Test Framework
Polyglot MCP test generation with 8-section contract enforcement across Python, TS, Java, Go, C++.
Connector by phoenice-labs · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/phoenice-labs-universal-test-framework
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 7 read · 5 write · 0 delete · 2 not yet classified
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Python package
Tools by what they do 14
Read from the source code; the running server may list different tools.
Read 7 · Look things up without changing anything.
analyze_coveragedetect_language_frameworkfeedback_statushealthquery_registrysuggest_test_typesvalidate_test_contract
Write 5 · Create, change, send or run things.
build_traceability_matriximport_test_resultsregister_contractsrun_mutation_testsrun_tests
Not yet classified 2 · We could not tell from the name and description.
generate_reportgenerate_tests
Files it touches
- Any path the agent passes to its tools
Tools (14)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
analyze_coverageAnalyze the coverage of a test suite and identify gaps. Args: tests: List of test dicts (output from generate_tests) source_code: Source code to identify uncovered symbols test_type: Test type for threshold lookup language: Language for tool recommendations Returns: covered_paths, uncovered_symbols, thresholds, recommendations
build_traceability_matrixBuild a requirements-to-tests traceability matrix. Args: tests: List of test dicts (must include test_id and requirement_mapping) requirements: Explicit list of requirement IDs to check coverage against Returns: matrix, matrix_markdown, summary, high_risk_uncovered, blocks_release
detect_language_frameworkDetect programming language and test framework from source code. Args: source_code: Source code to analyze file_path: Optional file path for extension-based detection Returns: language, framework, confidence, detected_from (evidence list)
feedback_statusGet UTF feedback loop status: gap analysis, coverage health, trend, and delta requirements. Args: project_id: Project to report on (defaults to current directory name) requirements: Requirements text to compare against registry for delta detection check_gaps: Run gap analysis and coverage health check (default: True) compute_trend: Compute coverage trend over time (default: True) trend_days: Number of days of history to include in trend (default: 30) project_dir: Absolute path to the caller's project root. Points the registry at <project_…
generate_reportGenerate the 8-section contract compliance report (Tool #12). Reads test records and execution results from the registry, builds the contract report in the requested formats, and returns report paths + summary. The 8-section contract lifecycle: generate_tests → enforcement → auto-report (this tool on demand) run_tests → execution binding → generate_report for unified view Args: formats: Output formats: subset of ["html", "junit", "json"]. Defaults to all three. open_html: Open the HTML report in the default browser (dev mode). project_id: Registry project…
generate_testsGenerate a complete test suite satisfying the 8-section test contract. The framework automatically: - Detects language and framework from source code - Generates tests for happy path, failure paths, and boundary cases - Validates every test against the 8-section contract before returning - Builds a traceability matrix linking tests to requirements - Identifies coverage gaps and makes recommendations Args: test_type: Type of tests to generate. One of: unit | integration | api | e2e | contract | performance | security source_code: Source code to analyze (function/class/m…
healthHealth check for the Universal Test Framework MCP server. Returns server status, version, and uptime. Suitable for use as a Docker HEALTHCHECK command, Kubernetes liveness/readiness probe, or basic availability verification. Returns: status : "ok" when the server is healthy version : UTF semantic version string uptime_s : seconds the server process has been running tools : number of registered MCP tools
import_test_resultsImport JUnit XML execution results into the UTF registry. Use this when you have already run tests with pytest / Maven / Go and want to register the results so that generate_report shows real pass/fail rates. Typical workflow: 1. Run tests: python -m pytest tests/ --junit-xml=utf-tests/reports/results.xml 2. Import: import_test_results("utf-tests/reports/results.xml") 3. Report: generate_report() Args: junit_xml_path: Path to the JUnit XML file (absolute or relative to project_dir). project_dir: Absolute path to caller's project root. Registry stored at …
query_registryQuery the UTF persistent test registry. Args: project_id: Filter by project (defaults to current directory name) test_type: Filter by test type (unit | integration | api | …) language: Filter by language (python | typescript | …) status: Filter by status (generated | executed | failed | gap) requirement_id: Filter tests that cover a specific requirement ID project_dir: Absolute path to the caller's project root. Points the registry query at <project_dir>/.utf/utf.db. Defaults to the current working direc…
register_contractsParse test files and register per-method 8-section contract records. This is the UTF registration bridge — it reads LLM-written test files, extracts the per-method 8-section comment blocks, and upserts status=generated rows into the UTF registry. Without this step, generate_report has no Per-Test Contract Detail cards. IMPORTANT — Phase 1, Step ③ of the UTF 3-phase workflow: ① generate_tests (scaffold) ② Write real test methods with per-method TC-{PRJ}-{MODULE}-{NNN} blocks ③ register_contracts ← this tool ④ generate_report (verify contract detail cards) ⑤ pytest --junit-xml=... …
run_mutation_testsRun mutation testing on a source+test file pair and return coverage metrics. Supports mutmut (Python), Stryker (JS/TS), PIT (Java), and gremlins (Go). The adapter is auto-detected based on language and tool availability. Args: source_file: Path to the source file to mutate test_file: Path to the test file to run against mutants language: Language of the files (python | javascript | typescript | java | go) project_dir: Project root directory (defaults to cwd) timeout_seconds: Mutation run timeout in seconds (default: 300) minimum_score: Threshold…
run_testsExecute test files and return structured results with CI annotations. Execution is always optional — controlled by UTF config. Never blocks generation. Args: test_files: List of test file paths to execute language: Language of the tests (python | typescript | javascript | java | go) framework: Test framework hint (pytest | vitest | jest | junit5 | maven | gradle | go) project_dir: Project root directory (defaults to cwd) timeout_seconds: Per-file execution timeout in seconds (default: 120) Returns: CI report with summary, per-file results, and G…
suggest_test_typesAnalyze code/requirements and suggest which test types to apply. Args: source_code: Source code to analyze requirements_text: Requirements or user stories Returns: recommended_types with priority and rationale, risk_flags
validate_test_contractValidate a test or test suite against the 8-section contract. Use this to check any existing test — generated or hand-written — for compliance. The contract requires all 8 sections: Test ID, Why Generated, Requirement Mapping, How it Exercises, Coverage Contribution, Expected Outcome, Gaps, Meaningfulness Check. Args: test_content: Raw markdown test text (paste any test here for quick validation) test_dict: Structured test as dict with 8-section keys tests_list: List of raw markdown strings for suite-level validation Returns: is_valid, score (0–1), missing_sections, violatio…
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 21
- Last commit
- Apr 14, 2026 (6 months ago)
- Last release
- Apr 14, 2026 (6 months ago)
- Last package publish
- Apr 14, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.phoenice-labs/universal-test-framework- Version
- 1.0.2
- Auth
- No auth
- Packages
- pypi universal-test-framework
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Cite this page
Universal Test Framework MCP server. Agent Mart. https://agentmart.dev/connectors/phoenice-labs-universal-test-framework (last updated 2026-10-24)