Server data from the Official MCP Registry
Connects MCP servers, packages, security checks, and release gates in one repo.
About
Connects MCP servers, packages, security checks, and release gates in one repo.
Security Report
ProdForge is a developer-tools MCP server and CLI whose code shows no exfiltration, backdoors, or obfuscation. Its main concerns are supply-chain and trust issues: the generated MCP config runs unpinned npm packages via npx -y, and the ship gate executes whatever binaries are named like fleet tools on PATH inside the user's project directory. Permissions broadly match its stated purpose of wiring tools, scaffolding projects, and running release checks. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
13 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cloudcorprecords-prodforge": {
"args": [
"-y",
"@reneturcios/prodforge"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
ProdForge
Take any product to production without wiring it all yourself.
You have the product idea. Then comes the hassle nobody warns you about: which MCP servers do I need, how do I connect them, what security checks matter, how do I know a release actually shipped, what breaks in production first?
ProdForge is one massive repo that already connected all of that together.
One catalog. One merged MCP config. Five production stacks. One ship gate.
npx @reneturcios/prodforge list
npx @reneturcios/prodforge connect --write mcp.json
npx @reneturcios/prodforge doctor
npx @reneturcios/prodforge checklist
npx @reneturcios/prodforge ship
npx @reneturcios/prodforge init cli-tool my-tool # real scaffold: files + tests
What is inside
- catalog/ - Every tool in the fleet in one registry: Greenlight, Shipcheck, Wallcheck, the Security Wave (hookcheck, actionpin, injectcheck, mcpvet, depguard, flowcheck, tracewatch), mcpaudit, cidiff, reprocheck, contextbudget, agentsfile, envdoc, npmpreflight, envdoctor, logdigest, and more. 26 tools, grouped by production phase: build, secure, test, release, operate.
- mcp/ - One merged MCP config that wires every shipped MCP server together at once, for Claude, Cursor, and VS Code. Stop copy-pasting server blocks one by one.
- stacks/ - Five production stacks you start from instead of a blank repo:
mcp-server,saas-web,api-service,cli-tool,ai-agent. Each stack says exactly which tools are pre-wired, which env vars it needs, and what its release gate is.prodforge init <stack> <name>generates a real one: package.json, tsconfig, README, src, and a passing test suite. - playbooks/ - The production playbook, the release playbook, the security playbook, and the observability playbook. Short, checkable, no fluff.
- CLI + MCP in one bin - Same fleet factory pattern as Greenlight and Shipcheck:
prodforgeis a CLI for humans and an MCP server for agents. Agents getlist_packages,connect_config,production_checklist,doctor_report,catalog_health, andship_gate.
Why this exists
Every tool in the catalog already shipped on its own: npm, GHCR, and the MCP Registry, with tests and real production validation. The pain was never any single tool. The pain was figuring out how they fit together while you are trying to ship a product.
ProdForge is that fit, done once, in public, and kept updated.
Start here
- Run
prodforge doctorin your project. Fix what it names. - Run
prodforge connect --write mcp.json. Your agent now has the whole fleet. - Pick a stack in
stacks/closest to your product and follow its checklist. - Before you tag anything, run
prodforge ship. It executes each installed fleet tool and reports the rest honestly: any FAIL is a NO-GO, a missing tool is ABSENT (never a PASS), and an unwired gate is NOT-WIRED. Exit 0 only on GO.
Stacks at a glance
| Stack | For | Pre-wired gates |
|---|---|---|
| mcp-server | A new MCP server | mcpaudit, mcpvet, shipcheck, npmpreflight |
| saas-web | A web SaaS product | wallcheck, flowcheck, envdoc, shipcheck |
| api-service | An API or backend service | depguard, flowcheck, logdigest, shipcheck |
| cli-tool | A CLI / dev tool | agentsfile, contextbudget, cidiff, shipcheck |
| ai-agent | An agent product | injectcheck, tracewatch, mcpvet, contextbudget |
Status
v0.5.0, built 2026-10-25 (Wave D: MCP catalog hardening, a vetting ledger covering all 27 registry tools, and a 107 server discovery list with every unvetted server kept out of the default profile). Overnight build log in docs/OVERNIGHT-2026-10-25.md. Roadmap in docs/ROADMAP.md - 5x the current scope, in waves.
MIT. By Rene Turcios / CloudCorpRecords. Fleet: https://github.com/CloudCorpRecords
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
