P4mcp Server
[Community Supported] Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system.
Is P4mcp Server safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare P4mcp Server
How does it stack up against its MCP Servers neighbours?
- ConnectWise Manage +0.2 higher
- Danishashko Yahoo Finance +0.2 higher
- Smart Connections MCP same score
In detail: P4mcp Server scores 49.7/100 (Grade D), ranked #941 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 54% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How P4mcp Server compares in MCP Servers
- #538 ConnectWise Manage 49.9 +0.2
- #539 Danishashko Yahoo Finance 49.9 +0.2
- #540 P4mcp Server 49.7 this agent
- #541 Smart Connections MCP 49.7 ±0
- #542 Switzerland MCP 🇨🇭 49.7 ±0
Bars show each HVTrust score; the tick marks P4mcp Server’s 49.7.
Where the 49.7 comes from
HVTrust dimensions vs the MCP Servers average
49.7 / 100 · 100.0% confidenceP4mcp Server MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
51.7 / 100Supply Chain Trust
Common questions about P4mcp Server
Does P4mcp Server publish package provenance?
Does P4mcp Server have an OpenSSF Scorecard?
Is P4mcp Server actively maintained?
What license does P4mcp Server use?
Are P4mcp Server's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to P4mcp Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain P4mcp Server?
For maintainers
HVTrust scores P4mcp Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/p4mcp-server)
<a href="https://hvtracker.net/agents/p4mcp-server"><img src="https://hvtracker.net/badge/p4mcp-server.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON