p4mcp-server (perforce/p4mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 75 out of 100, grade B. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Limited view
75/100
1 month ago

p4mcp-server

[Community Supported] Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system.

→ perforce/p4mcp-server· listed on github_topic

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

perforce

Source: github_topic · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHubGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLOG_LEVEL
🔐 secretGITHUB_TOKEN
configLOGSTASH_ENDPOINT
configREPO_OWNER
configREPO_NAME
configP4PORT"": "ssl:perforce.example.com:1666",
configP4USER"": "your_username",
configP4CLIENT"": "your_workspace"
configP4MCP_LOG_DIRDirectory for log files. Default: logs/ in the server executable's directory. Can be overridden by the --log-dir CLI argument.
configP4MCP_MAX_RESULTSPriority order: --max-results > > default (10000).
configP4MCP_MAX_SCAN_ROWSPriority order: --max-scan-rows > > default (unset).
configP4MCP_CA_BUNDLEcertifi: disable truststore injection and use default Python TLS certificate behavior. Custom CA bundles ( / --ca-bundle) take effect only in this mode.
configP4MCP_SSL_VERIFYSet to false to disable SSL verification for P4 Code Review API requests. Default: true. Works in both TLS modes.
configP4MCP_TLS_CA_MODETLS certificate source mode.
configOTEL_EXPORTER_OTLP_ENDPOINTOTLP collector endpoint for telemetry export. Default: https://grpc.public.prd.shared.perforce.com.
configOTEL_EXPORTER_OTLP_PROTOCOLOTLP export protocol. Only grpc is supported; other values fall back to grpc with a warning.
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — query_server (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); query_changelists (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); modify_changelists (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool handlers catch errors

Only 0/15 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/perforce/p4mcp-server)](https://m8ven.ai/mcp/perforce/p4mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6b43ba310182b54cf3960cc4cecfaa72ee1a07dd
code hash: 0b9838e04187d193615d71ca695d1602f5f603f0253f56983b9ff8a58fb132ed
verified: 8/7/2026, 2:13:11 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client