io.github.MUSE-CODE-SPACE/test-genie
NPM · TEST-GENIE-MCP · SCANNED SEP 20
AI-powered app test automation for iOS, Android, Flutter, React Native, Web
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 9.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 49 of 151 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 75 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1317 tokens (~69/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.MUSE-CODE-SPACE/test-genie MCP server?
io.github.MUSE-CODE-SPACE/test-genie runs locally as an npm package, launched with npx -y test-genie-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · test-genie-mcp
claude mcp add muse-code-space-test-genie -- npx -y test-genie-mcp
{
"mcpServers": {
"muse-code-space-test-genie": {
"command": "npx",
"args": [
"-y",
"test-genie-mcp"
]
}
}
} {
"servers": {
"muse-code-space-test-genie": {
"command": "npx",
"args": [
"-y",
"test-genie-mcp"
]
}
}
} codex mcp add muse-code-space-test-genie -- npx -y test-genie-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"muse-code-space-test-genie": {
"type": "local",
"command": [
"npx",
"-y",
"test-genie-mcp"
],
"enabled": true
}
}
} openclaw mcp add muse-code-space-test-genie --command npx --arg -y --arg test-genie-mcp
mcp_servers:
muse-code-space-test-genie:
command: "npx"
args: ["-y", "test-genie-mcp"] {
"McpServers": {
"muse-code-space-test-genie": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"test-genie-mcp"
]
}
}
} assistant mcp add muse-code-space-test-genie -t stdio -c npx -a -y test-genie-mcp
{
"mcpServers": {
"muse-code-space-test-genie": {
"command": "npx",
"args": [
"-y",
"test-genie-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/test-genie-mcp@2.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 151 packages
| Packages resolved | 151 |
|---|---|
| Deprecated | 2 |
| Stale | 47 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_app_structure ~80
Analyze app codebase structure including screens, components, APIs, and state management. Supports iOS, Android, Flutter, React Native, and Web platforms.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | Analysis depth level |
| platform | string | – | Target platform (auto-detected if not provided) |
| projectPath | string | yes | Path to the project root directory |
No output schema declared.
No examples provided.
analyze_code_deep ~50
Deep AST-based code analysis with function extraction, complexity metrics, hook analysis, and issue detection.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Target platform |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
analyze_performance ~49
Deep performance analysis including rendering, computation, network, and bundle size issues. Provides actionable recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Target platform |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
apply_fix ~65
Apply a confirmed fix to the codebase.
| Name | Type | Req | Description |
|---|---|---|---|
| backup | boolean | – | Create backup before applying |
| dryRun | boolean | – | Preview changes without applying |
| fixId | string | yes | ID of the fix to apply |
| validate | boolean | – | Validate syntax after applying |
No output schema declared.
No examples provided.
confirm_fix ~68
Confirm or reject a suggested fix before application.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Confirmation action |
| fixId | string | yes | ID of the fix to confirm |
| modifiedCode | string | – | Modified code if action is modify |
| reason | string | – | Reason for rejection if action is reject |
No output schema declared.
No examples provided.
create_test_plan ~92
Create a test plan from generated scenarios with filtering and scheduling options.
| Name | Type | Req | Description |
|---|---|---|---|
| maxDuration | number | – | Maximum duration in seconds |
| name | string | yes | Name of the test plan |
| priorityFilter | array | – | Filter by priority |
| projectPath | string | yes | Path to the project |
| template | string | – | Use a predefined template |
| typeFilter | array | – | Filter by test type |
No output schema declared.
No examples provided.
detect_logic_errors ~63
Detect logic errors including race conditions, state inconsistencies, null references, and type mismatches.
| Name | Type | Req | Description |
|---|---|---|---|
| analysisDepth | string | – | Analysis depth |
| checkTypes | array | – | Types of errors to check |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
detect_memory_leaks ~67
Detect memory leaks, retain cycles, and unclosed resources through static and dynamic analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| analysisType | string | – | Type of analysis |
| minLeakSizeMB | number | – | Minimum leak size to report (MB) |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
generate_cicd_config ~110
Generate CI/CD configuration for GitHub Actions, Jenkins, or GitLab CI with test automation integration.
| Name | Type | Req | Description |
|---|---|---|---|
| branches | array | – | Branches to run CI on |
| buildCommand | string | – | Custom build command |
| platform | string | – | Target platform |
| projectPath | string | yes | Path to the project |
| provider | string | yes | CI/CD provider |
| testCommand | string | – | Custom test command |
| writeToFile | boolean | – | Write config to project |
No output schema declared.
No examples provided.
generate_report ~66
Generate detailed test automation report in Markdown, HTML, or JSON format.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Report format |
| outputPath | string | – | Path to save the report |
| projectPath | string | yes | Path to the project |
| sections | array | – | Sections to include |
No output schema declared.
No examples provided.
generate_scenarios ~97
Generate test scenarios based on app structure analysis. Creates E2E, integration, unit, performance, and memory test scenarios.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | – | Coverage level |
| focusAreas | array | – | Specific areas to focus on |
| maxScenarios | number | – | Maximum number of scenarios to generate |
| projectPath | string | yes | Path to the project |
| testTypes | array | – | Types of tests to generate |
No output schema declared.
No examples provided.
get_pending_fixes ~32
Get list of pending fix suggestions waiting for confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
get_test_history ~40
Get test execution history for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results to return |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
rollback_fix ~32
Rollback an applied fix to restore original code.
| Name | Type | Req | Description |
|---|---|---|---|
| fixId | string | yes | ID of the fix to rollback |
No output schema declared.
No examples provided.
run_full_automation ~93
Run complete test automation pipeline: analyze → generate scenarios → run tests → detect issues → suggest fixes. Interactive confirmation for fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| autoFix | boolean | – | Automatically apply high-confidence fixes |
| confirmMode | string | – | Fix confirmation mode |
| platform | string | – | Target platform |
| projectPath | string | yes | Path to the project |
| testTypes | array | – | Types of tests to run |
No output schema declared.
No examples provided.
run_scenario_test ~87
Run a specific test scenario and get detailed results.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Target device or simulator |
| platform | string | yes | Target platform |
| projectPath | string | yes | Path to the project |
| retries | number | – | Number of retry attempts |
| scenarioId | string | yes | ID of the scenario to run |
| timeout | number | – | Timeout in milliseconds |
No output schema declared.
No examples provided.
run_simulation ~79
Run user behavior simulation to find issues through random/pattern-based testing.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | number | yes | Simulation duration in seconds |
| intensity | string | – | Interaction intensity |
| monitorMetrics | array | – | Metrics to monitor |
| projectPath | string | yes | Path to the project |
| userPatterns | array | – | User behavior patterns to simulate |
No output schema declared.
No examples provided.
run_stress_test ~92
Run stress/load tests on APIs or UI components.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | number | yes | Number of concurrent users/requests |
| duration | number | yes | Test duration in seconds |
| endpoints | array | – | Specific endpoints to test |
| projectPath | string | yes | Path to the project |
| rampUp | number | – | Ramp up time in seconds |
| targetType | string | yes | What to stress test |
No output schema declared.
No examples provided.
suggest_fixes ~55
Generate AI-powered fix suggestions for detected issues.
| Name | Type | Req | Description |
|---|---|---|---|
| issueIds | array | – | Specific issue IDs to fix |
| maxSuggestions | number | – | Maximum suggestions to generate |
| projectPath | string | yes | Path to the project |
No output schema declared.
No examples provided.
What is the io.github.MUSE-CODE-SPACE/test-genie MCP server?
io.github.MUSE-CODE-SPACE/test-genie is an MCP server listed in the public MCP registry as io.github.MUSE-CODE-SPACE/test-genie. AI-powered app test automation for iOS, Android, Flutter, React Native, Web. This page covers its npm package (test-genie-mcp).
Is the io.github.MUSE-CODE-SPACE/test-genie MCP server safe to use?
io.github.MUSE-CODE-SPACE/test-genie scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.MUSE-CODE-SPACE/test-genie MCP server expose?
io.github.MUSE-CODE-SPACE/test-genie exposes 19 tools: analyze_app_structure, generate_scenarios, create_test_plan, run_scenario_test, run_simulation, and 14 more. Their descriptions and schemas cost roughly 1,317 tokens of context every time the server is loaded.
Is the io.github.MUSE-CODE-SPACE/test-genie MCP server still maintained?
io.github.MUSE-CODE-SPACE/test-genie is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.MUSE-CODE-SPACE/test-genie MCP server under?
io.github.MUSE-CODE-SPACE/test-genie declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.