ProdForge
NPM · @RENETURCIOS/PRODFORGE · 2 COMPONENTS
Connects MCP servers, packages, security checks, and release gates in one repo.
Available components
Last scanned (23 hours ago)
Scores higher than 34% of npm servers
Category CI/CD and DevOps
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 186 tokens (~31/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 63
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@reneturcios/prodforge@0.5.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
catalog_health ~23
Validate the ProdForge catalog itself: duplicates, missing fields, bad phases.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connect_config ~20
Return one merged MCP config wiring every shipped MCP server together.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
doctor_report ~19
Run local production-readiness checks on the current project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_packages ~42
List every package ProdForge can wire together, optionally by production phase.
| Name | Type | Req | Description |
|---|---|---|---|
| phase | string | – | Only list tools in this production phase; omit to list every tool. |
No output schema declared.
No examples provided.
production_checklist ~26
The full production checklist, grouped by phase, with the tool that runs each step.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ship_gate ~56
Run the release gate: executes each installed fleet tool in the given directory, reports ABSENT when missing, never fakes a PASS.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Directory to run the release gate in; defaults to the current working directory. |
No output schema declared.
No examples provided.
How do I install the ProdForge MCP server?
ProdForge runs locally as an npm package, launched with npx -y @reneturcios/prodforge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/prodforge
claude mcp add cloudcorprecords-prodforge -- npx -y @reneturcios/prodforge
What is the ProdForge MCP server?
ProdForge is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/prodforge. Connects MCP servers, packages, security checks, and release gates in one repo. This page covers its npm package (@reneturcios/prodforge).
Is the ProdForge MCP server safe to use?
ProdForge scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 ProdForge MCP server expose?
ProdForge exposes 6 tools: list_packages, connect_config, production_checklist, doctor_report, ship_gate, catalog_health. Their descriptions and schemas cost roughly 186 tokens of context every time the server is loaded.
Is the ProdForge MCP server still maintained?
ProdForge is still listed as active in the MCP registry. We last reached this channel on 4 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 ProdForge MCP server under?
ProdForge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.