repo-test-architect

MCPcommunity
v1.0.0-beta.2io.github.RepoAssayMITUpdated 29d agonpmGitHub

Audit-first test strategy MCP server for repository-native test planning.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
29d agoLast update
Package
Authorio.github.RepoAssay
LicenseMIT
Version1.0.0-beta.2
Sourcenpm+mcp-registry
npmrepo-test-architect
GitHubrepoassay/repo-test-architect
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface19 tools · 1 privileged
Security scan✓ Cleanv0.3.0 · 1mo agoHow well does this scan work?
MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive
EvalsNone
IndexedJul 25, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

19 tools · 1 privileged
Statically extracted from the published packagev0.3.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

analyze_repositoryNo description published

This tool published no description. Forge does not invent one.

list_adaptersNo description published

This tool published no description. Forge does not invent one.

list_project_detection_rulesNo description published

This tool published no description. Forge does not invent one.

detect_projectsNo description published

This tool published no description. Forge does not invent one.

audit_projectsNo description published

This tool published no description. Forge does not invent one.

summarize_project_auditsNo description published

This tool published no description. Forge does not invent one.

rank_project_candidatesNo description published

This tool published no description. Forge does not invent one.

generate_project_test_planNo description published

This tool published no description. Forge does not invent one.

collect_project_findingsNo description published

This tool published no description. Forge does not invent one.

analyze_project_test_placementNo description published

This tool published no description. Forge does not invent one.

collect_project_statsNo description published

This tool published no description. Forge does not invent one.

audit_repoNo description published

This tool published no description. Forge does not invent one.

get_audit_graphNo description published

This tool published no description. Forge does not invent one.

generate_test_planNo description published

This tool published no description. Forge does not invent one.

get_plan_execution_hintsprivilegedNo description published

This tool published no description. Forge does not invent one.

explain_targetNo description published

This tool published no description. Forge does not invent one.

rank_test_candidatesNo description published

This tool published no description. Forge does not invent one.

analyze_test_placementNo description published

This tool published no description. Forge does not invent one.

generate_selected_testNo description published

This tool published no description. Forge does not invent one.

0 of 19 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Audit-first test strategy MCP server for repository-native test planning.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in testing & ci