Is io.github.phoenice-labs/universal-test-framework safe to use?

io.github.phoenice-labs/universal-test-framework has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.phoenice-labs/universal-test-framework?

io.github.phoenice-labs/universal-test-framework supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

Is io.github.phoenice-labs/universal-test-framework actively maintained?

io.github.phoenice-labs/universal-test-framework is actively maintained — last commit was 0 days ago.

io.github.phoenice-labs/universal-test-framework

Polyglot MCP test generation with 8-section contract enforcement across Python, TS, Java, Go, C++.

ActiveNot tested

Legal

PyPI GitHub

55CNo CVEsactive

Quick Install

{
  "mcpServers": {
    "utf": {
      "cwd": "${workspaceFolder}",
      "env": {
        "UTF_PROJECT_DIR": "${workspaceFolder}"
      },
      "args": [
        "--from",
        "universal-test-framework",
        "utf-server",
        "--transport",
        "stdio"
      ],
      "command": "uvx"
    }
  }
}

Setup guide

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-phoenice-labs-universal-test-framework)](https://mcppedia.org/s/io-github-phoenice-labs-universal-test-framework)

Should you use this server?

> Contract-driven test enforcement and reporting for LLM-generated code — via MCP, VS Code, Copilot CLI, Claude, Cursor, or Python SDK.

✓

Is it safe?

No known CVEs for universal-test-framework.

No authentication — any process on your machine can connect.

License not specified.

✓

Is it maintained?

Last commit 0 days ago.

Will it work with my client?

Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

Universal Test Framework (UTF)

Contract-driven test enforcement and reporting for LLM-generated code — via MCP, VS Code, Copilot CLI, Claude, Cursor, or Python SDK.

UTF is an MCP server and contract enforcement engine. It does not replace your AI coding assistant — it gives every test your AI writes a mandatory quality gate, a structured audit trail, and a comprehensive compliance report.

Why UTF? (Not Another Test Generator)

AI tools — GitHub Copilot, Claude, Cursor, Gemini — generate tests fast. The problem: fast ≠ trustworthy.

Without UTF	With UTF
Tests exist but nobody knows why	Every test is linked to a requirement
"Covers everything" — nobody can prove it	Traceability matrix maps REQ → test
CI passes; real behavior untested	Gap analysis flags what is NOT covered
LLM wrote a test that asserts `True`	Meaningfulness check rejects trivial assertions
No history of what was tested	Persistent registry survives session restarts
Report shows pass/fail counts only	8-section per-test detail cards in HTML report

UTF vs Markdown Instructions / Prompt Files

You may already use markdown files (AGENTS.md, copilot-instructions.md, .cursorrules) to guide your AI. UTF is complementary — not competing:

Markdown instructions	UTF
Describe how to write tests	Enforce a contract on every test produced
Rely on LLM to follow instructions	Block tests that fail the contract at generation time
No verification after generation	Score each test 0–1 against 8 measurable criteria
No persistent state between sessions	SQLite registry persists all tests and results
No compliance report	HTML report with per-test 8-section detail cards

Use markdown instructions to shape how your AI thinks. Use UTF to verify and report on what it produced.

Key Features

13 MCP tools — generate, validate, register, analyze, trace, execute, mutate, report, and query tests
6 languages — Python, TypeScript, JavaScript, Java, Go, C++
7 test types — unit, integration, API, E2E, contract, performance, security
8-section contract — every test must pass all 8 sections or it is blocked (minimum score: 0.85)
3-segment test IDs — TC-{PRJ}-{MODULE}-{NNN} and classic TC-{MODULE}-{NNN} both accepted
Five install modes — uvx (zero-clone), local clone, Docker, GitHub MCP Registry, pip SDK
VS Code @utf — chat participant with slash commands
CI/CD ready — GitHub Actions, GitLab CI, pre-commit hooks
Per-project overrides — YAML rules in .utf/rules/ override global defaults

Quick Start

Setup Method Comparison

#	Method	How Started	Registry Location	`@utf` Slash Cmds	Best For
1	uvx (zero-install)	`mcp.json` + uvx	`<workspace>/.utf/utf.db`	❌ use natural language	Any developer with uv
2	Local Clone	`install-vscode-mcp.ps1`	`<workspace>/.utf/utf.db`	✅ with extension	Contributing / customizing UTF
3	Docker / HTTP	`docker compose up`	Named volume or bind mount	❌ use natural language	Team / remote / CI
4	GitHub MCP Registry	Auto via client	`<workspace>/.utf/utf.db`	❌ use natural language	Discoverable via MCP marketplace
5	pip + SDK	Python import	Caller controls cwd	N/A	CI scripts / programmatic

All methods (1, 2, 4) using stdio transport write the registry to **`${wor

... View full README on GitHub

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

uvx 'universal-test-framework' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Score Breakdown

MCPpedia Score

Click each category to see evidence

55C

Last scored 9h ago

How we score →

Security

19/30

No known vulnerabilities.

✓

Known CVEs — No known CVEs for universal-test-frameworkcheck OSV.dev

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

○

Tool stability — First scan — baseline recorded

○

Dependency health — found on deps.dev, recently updated

✗

License — No license specified

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.phoenice-labs/universal-test-framework safe to use?: io.github.phoenice-labs/universal-test-framework has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.phoenice-labs/universal-test-framework?: io.github.phoenice-labs/universal-test-framework supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.phoenice-labs/universal-test-framework?: io.github.phoenice-labs/universal-test-framework is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio and sse and http transport.
Is io.github.phoenice-labs/universal-test-framework actively maintained?: io.github.phoenice-labs/universal-test-framework is actively maintained — last commit was 0 days ago.

Similar servers

View all →

A11y Mcp

No CVEs91A

An MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Amp/Cline/Cursor/GH Copilot) and let them fix a11y issues for you!

2 toolsremote39157.3k/wk24d ago

Luxembourg Law MCP Server

No CVEs87A

Luxembourg legislation via MCP — full-text search across statutes and provisions

7 toolsremote11/wk4d ago

Stratum MCP Server

No CVEs87A

Structured execution for Claude Code — contracts, postconditions, gates, guardrails.

3 toolsremote36d ago

Belgian Law MCP Server

No CVEs87A

Belgian legislation via MCP — full-text search across statutes and provisions

8 toolsremote7/wk6d ago

MCP Security Weekly

Get CVE alerts and security updates for io.github.phoenice-labs/universal-test-framework and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Universal Test Framework (UTF)

Contract-driven test enforcement and reporting for LLM-generated code — via MCP, VS Code, Copilot CLI, Claude, Cursor, or Python SDK.

Why UTF? (Not Another Test Generator)

AI tools — GitHub Copilot, Claude, Cursor, Gemini — generate tests fast. The problem: fast ≠ trustworthy.

Without UTF	With UTF
Tests exist but nobody knows why	Every test is linked to a requirement
"Covers everything" — nobody can prove it	Traceability matrix maps REQ → test
CI passes; real behavior untested	Gap analysis flags what is NOT covered
LLM wrote a test that asserts `True`	Meaningfulness check rejects trivial assertions
No history of what was tested	Persistent registry survives session restarts
Report shows pass/fail counts only	8-section per-test detail cards in HTML report

UTF vs Markdown Instructions / Prompt Files

You may already use markdown files (AGENTS.md, copilot-instructions.md, .cursorrules) to guide your AI. UTF is complementary — not competing:

Markdown instructions	UTF
Describe how to write tests	Enforce a contract on every test produced
Rely on LLM to follow instructions	Block tests that fail the contract at generation time
No verification after generation	Score each test 0–1 against 8 measurable criteria
No persistent state between sessions	SQLite registry persists all tests and results
No compliance report	HTML report with per-test 8-section detail cards

Use markdown instructions to shape how your AI thinks. Use UTF to verify and report on what it produced.

Key Features

13 MCP tools — generate, validate, register, analyze, trace, execute, mutate, report, and query tests
6 languages — Python, TypeScript, JavaScript, Java, Go, C++
7 test types — unit, integration, API, E2E, contract, performance, security
8-section contract — every test must pass all 8 sections or it is blocked (minimum score: 0.85)
3-segment test IDs — TC-{PRJ}-{MODULE}-{NNN} and classic TC-{MODULE}-{NNN} both accepted
Five install modes — uvx (zero-clone), local clone, Docker, GitHub MCP Registry, pip SDK
VS Code @utf — chat participant with slash commands
CI/CD ready — GitHub Actions, GitLab CI, pre-commit hooks
Per-project overrides — YAML rules in .utf/rules/ override global defaults

Quick Start

Setup Method Comparison

#	Method	How Started	Registry Location	`@utf` Slash Cmds	Best For
1	uvx (zero-install)	`mcp.json` + uvx	`<workspace>/.utf/utf.db`	❌ use natural language	Any developer with uv
2	Local Clone	`install-vscode-mcp.ps1`	`<workspace>/.utf/utf.db`	✅ with extension	Contributing / customizing UTF
3	Docker / HTTP	`docker compose up`	Named volume or bind mount	❌ use natural language	Team / remote / CI
4	GitHub MCP Registry	Auto via client	`<workspace>/.utf/utf.db`	❌ use natural language	Discoverable via MCP marketplace
5	pip + SDK	Python import	Caller controls cwd	N/A	CI scripts / programmatic

All methods (1, 2, 4) using stdio transport write the registry to **`${wor

... View full README on GitHub