Arch Master Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Arch Master Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Multi-stack scaffolding engine exposed as a Model Context Protocol (MCP) server. Generates production-ready module structures for NestJS, Java Spring, and Python FastAPI — directly from any MCP-compatible AI client.
Zero-token boilerplate. Designed for projects that are just getting started — instead of asking the AI to write every file (which burns thousands of tokens), the AI simply calls a tool and the entire module structure is generated locally on your machine in milliseconds.
Arch-Master MCP exposes two tools over stdio:
| Tool | Description |
|---|---|
scaffold_module | Generates all architecture files for a named module in the chosen stack/pattern |
list_patterns | Returns a markdown table of every supported stack and its available patterns |
No files are uploaded to the AI. All generation runs locally — only the file list is returned to the client.
When starting a project from scratch, the AI would normally write every file from scratch — entity, repository, service, controller, module, interfaces, mappers — burning thousands of output tokens per module. Arch-Master flips this: the AI decides what to generate, the MCP generates how.
| Approach | Tokens per module (approx.) |
|---|---|
| AI writes each file manually | ~2 000 – 5 000 tokens |
scaffold_module via Arch-Master | ~50 – 100 tokens |
| Stack | Patterns | Base path |
|---|---|---|
nestjs | hexagonal, layers, clean | src/modules |
java_spring | hexagonal, layers, clean | src/main/java/com/company/modules |
python_fastapi | hexagonal, layers, clean | src/modules |
pnpm installpnpm build
# output → dist/{
"mcpServers": {
"arch-master": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "/absolute/path/to/arch-master-mcp"
}
}
}pnpm test # unit tests (Jest)
pnpm test:cov # coverage report
pnpm build # compile TypeScript → dist/src/
├── index.ts # MCP server entry point (tool registration)
├── core/
│ ├── generator.ts # File creation engine
│ └── template-engine.ts # {{Variable}} template renderer
├── handlers/
│ └── scaffold.handler.ts # Tool request handlers
├── strategies/
│ ├── index.ts # Strategy registry (single source of truth)
│ ├── hexagonal/ # Hexagonal pattern templates per stack
│ ├── layers/ # Layered pattern templates per stack
│ └── clean/ # Clean architecture templates per stack
├── types/
│ └── mcp-types.ts # Shared TypeScript interfaces
└── utils/
└── file-system.ts # fs helperssrc/strategies/index.ts and its pattern files under src/strategies/<pattern>/.src/strategies/index.ts.src/index.ts entry point is generic — it never needs to change.NodeNext module resolution)@modelcontextprotocol/sdkdist/~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.