Repo Test Architect
NPM · REPO-TEST-ARCHITECT
Audit-first test strategy MCP server for repository-native test planning.
Available components
Last scanned (22 hours ago)
Scores higher than 86% of npm servers
Category Testing and QA
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 99 dependencies flagged as unhealthy. 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1607 tokens (~84/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 20 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: excellent → good functional
- Package version: 1.0.1 → 1.1.0 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.0 → 1.0.1 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Package version: 0.3.0 → 1.0.0 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/repo-test-architect@1.1.0
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 →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 30 |
| 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_project_test_placement Analyze Project Test Placement ~101
Derive advisory test-placement findings across an existing project-audits/v1 artifact while preserving project identity. Use this for multiple audited projects; use analyze_test_placement for one audit/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | The project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditCoverage | – | – | – |
| failedProjectCount | integer | – | – |
| failedProjects | array | – | – |
| findings | array | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
analyze_repository Analyze Repository ~132
Start here for an unfamiliar repository or a general test-architecture review. Detect and audit all project roots once, then return the complete deterministic summary, blockers, findings, ranking, plan, execution hints, verification commands, and stats. Prefer this over audit_repo unless one project root and adapter were explicitly selected.
| Name | Type | Req | Description |
|---|---|---|---|
| changedPaths | array | – | Optional repository-relative source paths to limit target selection inside detected projects. |
| excludeProjectRoots | array | – | Optional exact project roots or subtree patterns such as examples/** to exclude before analysis. |
| goTarget | object | – | – |
| repoRoot | string | yes | Repository root path. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditSummary | object | yes | – |
| candidateRanking | object | yes | – |
| executionHints | object | yes | – |
| findings | object | yes | – |
| projectAudits | object | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| stats | object | yes | – |
| summary | object | yes | – |
| testPlan | object | yes | – |
| verificationCommands | array | yes | – |
No examples provided.
analyze_test_placement Analyze Test Placement ~125
Derive advisory test-placement findings from an existing single-project audit/v1 artifact. Use this for one audited project; use analyze_project_test_placement for a project-audits/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | The audit/v1 object returned by audit_repo or contained in projectAudits.audits[].audit; pass the artifact itself, not a file path. |
| owner | string | – | Optional owner label for the audited project. Defaults to audit.profile.root. |
| Name | Type | Req | Description |
|---|---|---|---|
| auditCoverage | – | – | – |
| failedProjectCount | integer | – | – |
| failedProjects | array | – | – |
| findings | array | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
audit_projects Audit Projects ~124
Return raw per-project audit artifacts for all detected supported roots, report unsupported roots, and list roots whose adapter failed in failedProjects. Use when a downstream specialist tool needs project-audits/v1; for a complete first-pass review, prefer analyze_repository.
| Name | Type | Req | Description |
|---|---|---|---|
| changedPaths | array | – | Optional repository-relative source paths to limit target selection inside detected projects. |
| excludeProjectRoots | array | – | Optional exact project roots or subtree patterns such as examples/** to exclude before auditing detected projects. |
| goTarget | object | – | – |
| repoRoot | string | yes | Repository root path. |
| Name | Type | Req | Description |
|---|---|---|---|
| audits | array | yes | – |
| failedProjects | array | – | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| skippedProjects | array | yes | – |
| summary | object | yes | – |
No examples provided.
audit_repo Audit Repository ~102
Audit one explicitly selected project root and return audit/v1. Use only when the caller selected a single adapter or project boundary; adapterId defaults to javascript. For an unfamiliar or complete repository review, use analyze_repository.
| Name | Type | Req | Description |
|---|---|---|---|
| adapterId | string | – | Optional adapter id. Defaults to javascript. |
| changedPaths | array | – | Optional repository-relative source paths to limit target selection. |
| goTarget | object | – | – |
| repoRoot | string | yes | Repository root path. |
| Name | Type | Req | Description |
|---|---|---|---|
| coveredButRisky | array | yes | – |
| profile | object | yes | – |
| recommended | array | yes | – |
| risks | array | yes | – |
| schemaVersion | – | yes | – |
| skipped | array | yes | – |
| untestedCandidates | array | yes | – |
No examples provided.
collect_project_findings Collect Project Findings ~49
Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | A project-audits/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| failedProjects | array | – | – |
| findings | array | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
| unsupportedProjects | array | yes | – |
No examples provided.
collect_project_stats Collect Project Stats ~101
Aggregate coverage, counts, risk and signal distributions, frameworks, and adapter usage from an existing project-audits/v1 artifact. Use this for separate reporting or comparisons; analyze_repository already includes the same stats. Returns project-stats/v1 without rescanning the repository, executing tests, or writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | The project-audits/v1 object returned by audit_projects; pass the artifact itself, not a file path. |
| Name | Type | Req | Description |
|---|---|---|---|
| adapters | array | yes | – |
| counts | object | yes | – |
| distributions | object | yes | – |
| failedProjects | array | – | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| sourceFiles | object | yes | – |
| summary | object | yes | – |
No examples provided.
detect_projects Detect Projects ~105
Discover project roots, support status, and matching adapters without auditing source targets. Use this when project boundaries are needed before a specialized workflow; use analyze_repository for a complete review. Reads local repository markers and returns project-detection/v1 without executing tests or writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeProjectRoots | array | – | Optional exact project roots or subtree patterns such as examples/** to exclude before returning detected projects. |
| repoRoot | string | yes | Readable repository directory whose project markers should be inspected. |
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
No examples provided.
explain_target Explain Audit Target ~133
Explain the evidence, risk, testability, and recommendation for one target in an existing audit/v1 artifact. Use this after audit_repo or audit_projects when one target needs detail beyond the audit summary. Returns target-explanation/v1 without rescanning the repository, executing tests, or writing files.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | The audit/v1 object returned by audit_repo or contained in projectAudits.audits[].audit; pass the artifact itself, not a file path. |
| targetId | string | yes | Exact stable id from an audit target in untestedCandidates, coveredButRisky, recommended, or skipped. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | yes | – |
| existingTestEvidence | array | – | – |
| existingTestPaths | array | yes | – |
| kind | string | yes | – |
| maintenanceCost | integer | yes | – |
| path | string | yes | – |
| rationale | array | yes | – |
| recommendation | – | yes | – |
| risk | – | yes | – |
| riskReductionScore | integer | yes | – |
| schemaVersion | – | yes | – |
| signals | array | yes | – |
| target | string | yes | – |
| targetId | string | yes | – |
| testLevel | – | yes | – |
| testability | – | yes | – |
No examples provided.
generate_project_test_plan Generate Project Test Plan ~50
Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | A project-audits/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| failedProjects | array | – | – |
| items | array | yes | – |
| projectPlans | array | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
| unsupportedProjects | array | yes | – |
No examples provided.
generate_selected_test Generate Selected Test (Deferred) ~47
Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled.
| Name | Type | Req | Description |
|---|---|---|---|
| planItemId | string | yes | Stable plan item id selected for future generation. |
| Name | Type | Req | Description |
|---|---|---|---|
| nextSteps | array | yes | – |
| planItemId | string | yes | – |
| reason | string | yes | – |
| schemaVersion | – | yes | – |
| status | – | yes | – |
No examples provided.
generate_test_plan Generate Test Plan ~126
Create a deterministic plan/v1 from an existing single-project audit/v1 artifact. Use this after audit_repo, optionally selecting one exact plan item; use generate_project_test_plan for multiple audited projects. Does not rescan the repository, execute tests, or generate or write test code.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | The audit/v1 object returned by audit_repo or contained in projectAudits.audits[].audit; pass the artifact itself, not a file path. |
| itemId | string | – | Optional exact plan item id to return; omit it to return the complete deterministic plan. |
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | array | yes | – |
| items | array | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
No examples provided.
get_audit_graph Get Audit Graph ~50
Validate and return an existing audit/v1 artifact unchanged; this does not scan a repository. Use audit_repo or analyze_repository for repository discovery.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | An audit/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| coveredButRisky | array | yes | – |
| profile | object | yes | – |
| recommended | array | yes | – |
| risks | array | yes | – |
| schemaVersion | – | yes | – |
| skipped | array | yes | – |
| untestedCandidates | array | yes | – |
No examples provided.
get_plan_execution_hints Get Plan Execution Hints ~75
Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | – | Optional stable plan item or project item id to select. |
| plan | object | yes | A plan/v1 or project-test-plan/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| failedProjects | array | – | – |
| items | array | yes | – |
| schemaVersion | – | yes | – |
| source | object | yes | – |
| summary | object | yes | – |
No examples provided.
list_adapters List Adapters ~18
List registered language adapters available to audit repositories.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| adapters | array | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
list_project_detection_rules List Project Detection Rules ~23
List deterministic project marker rules and ignored directories used during project detection.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| fallbackRules | array | – | – |
| ignoredDirectories | array | yes | – |
| markers | array | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
rank_project_candidates Rank Project Test Candidates ~50
Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | A project-audits/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| failedProjects | array | – | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
| unsupportedProjects | array | yes | – |
No examples provided.
rank_test_candidates Rank Test Candidates ~33
Rank testable audit targets by risk reduction and maintenance cost.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | An audit/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| blockers | array | yes | – |
| candidates | array | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
No examples provided.
summarize_project_audits Summarize Project Audits ~59
Summarize an existing project-audits/v1 artifact. Use only when a compact coverage view is needed separately; analyze_repository already includes this result.
| Name | Type | Req | Description |
|---|---|---|---|
| projectAudits | object | yes | A project-audits/v1 artifact. |
| Name | Type | Req | Description |
|---|---|---|---|
| failedProjects | array | – | – |
| projects | array | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| summary | object | yes | – |
| unsupportedProjects | array | yes | – |
No examples provided.
How do I install the Repo Test Architect MCP server?
Repo Test Architect runs locally as an npm package, launched with npx -y repo-test-architect 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 · repo-test-architect
claude mcp add repoassay-repo-test-architect -- npx -y repo-test-architect mcp
What is the Repo Test Architect MCP server?
Repo Test Architect is an MCP server listed in the public MCP registry as io.github.RepoAssay/repo-test-architect. Audit-first test strategy MCP server for repository-native test planning. This page covers its npm package (repo-test-architect).
Is the Repo Test Architect MCP server safe to use?
Repo Test Architect scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Repo Test Architect MCP server expose?
Repo Test Architect exposes 19 tools: analyze_repository, list_adapters, list_project_detection_rules, detect_projects, audit_projects, and 14 more. Their descriptions and schemas cost roughly 1,503 tokens of context every time the server is loaded.
Is the Repo Test Architect MCP server still maintained?
Repo Test Architect is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Repo Test Architect MCP server under?
Repo Test Architect declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Repo Test Architect MCP server?
VerifyMCP ran 16 checks on Repo Test Architect, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.