Perforce (iPraBhu) MCP Server
mcp-perforce-server
npm
v3.3.0
Published by iprabhu — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Enterprise-grade MCP (Model Context Protocol) server for Perforce P4 integration with AI assistants. Includes 59 MCP tools, native-style batch and flag support, rich review/search workflow helpers, and comprehensive security controls such as audit logging
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (dist/p4/runner.js)MTC-SRC-002
In the server's implementation (`dist/p4/runner.js:37`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: 4Runner = void 0; const child_process_1 = require("child_process"); const os = __importStar(require("os")); function get
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/p4/runner.js
Tools 59
Each tool and what it can reach — statically extracted from the published source.
p4.filesreads sensitive datap4.havereads sensitive datap4.addno sensitive capabilityp4.annotateno sensitive capabilityp4.auditno sensitive capabilityp4.blameno sensitive capabilityp4.change.inspectno sensitive capabilityp4.changelist.createno sensitive capabilityp4.changelist.submitno sensitive capabilityp4.changelist.updateno sensitive capability
Show 49 more tools ↓
p4.changesno sensitive capabilityp4.clientno sensitive capabilityp4.clientsno sensitive capabilityp4.complianceno sensitive capabilityp4.config.detectno sensitive capabilityp4.copyno sensitive capabilityp4.deleteno sensitive capabilityp4.describeno sensitive capabilityp4.diffno sensitive capabilityp4.diff2no sensitive capabilityp4.dirsno sensitive capabilityp4.editno sensitive capabilityp4.file.inspectno sensitive capabilityp4.filelogno sensitive capabilityp4.fixesno sensitive capabilityp4.fstatno sensitive capabilityp4.grepno sensitive capabilityp4.infono sensitive capabilityp4.integrateno sensitive capabilityp4.integratedno sensitive capabilityp4.interchangesno sensitive capabilityp4.jobno sensitive capabilityp4.jobsno sensitive capabilityp4.labelno sensitive capabilityp4.labelsno sensitive capabilityp4.mergeno sensitive capabilityp4.moveno sensitive capabilityp4.openedno sensitive capabilityp4.path.synccheckno sensitive capabilityp4.printno sensitive capabilityp4.resolveno sensitive capabilityp4.revertno sensitive capabilityp4.reviewno sensitive capabilityp4.review.bundleno sensitive capabilityp4.review.prepareno sensitive capabilityp4.reviewsno sensitive capabilityp4.search.inspectno sensitive capabilityp4.shelveno sensitive capabilityp4.sizesno sensitive capabilityp4.statusno sensitive capabilityp4.streamno sensitive capabilityp4.streamsno sensitive capabilityp4.submitno sensitive capabilityp4.syncno sensitive capabilityp4.unshelveno sensitive capabilityp4.userno sensitive capabilityp4.usersno sensitive capabilityp4.whereno sensitive capabilityp4.workspace.snapshotno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (59 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v3.3.0 latest |
A 93/100 | 1 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-perforce-server --onlineOther implementations of Perforce 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.