p4mcp-server@2026.4.3126709
VERIFIED· not startedPublisher claims: "P4 MCP Server - Model Context Protocol server for Perforce P4 version control and P4 DAM digital asset management" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
P4DAM_API_KEYConfiguration, not credentials: OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_PROTOCOL, P4CLIENT, P4MCP_CA_BUNDLE, P4MCP_LOG_DIR, P4MCP_MAX_RESULTS, P4MCP_MAX_SCAN_ROWS, P4MCP_SSL_VERIFY, P4MCP_TLS_CA_MODE, P4PORT, P4USER- Where it talks to
- no vendor host named in the codeAlso perforce.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names perforce.com as well as its own vendor. The guard injects P4DAM_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
https://github.com/perforce/p4mcp-server/releases/latest/download/p4-mcp-server-mac.zipFix: Pin versions and sources; vendor anything fetched at install time.### Admin configurationFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>uvx (easiest, no install required)</b></summary> If you have [uv](https://docs.astral.sh/uv/) installed, you can run P4 MCP Server directly without Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Local</b></summary> Run the P4 MCP Server directly on your machine using the default STDIO transport. Add the following to your `mcp.json`: ```json Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>VM</b></summary> Run the MCP server on a VM using the HTTP transport, allowing clients to connect over the network. **Start the server on the VM:** Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.subprocess.run([sys.executable, "-m", "p4mcp.telemetry.consent_ui"], check=True)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.subprocess.run([str(consent_ui)], check=True)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.<summary><b>Docker</b></summary> Run the P4 MCP Server from a Docker container with STDIO transport, allowing MCP clients to manage the container lifecycle. > *Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Docker</b></summary> Run the MCP server in a Docker container using HTTP transport and expose the MCP endpoint over a host port. **Start the containFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for p4mcp-server@2026.4.3126709 as of 5 h ago. This is the package itself, not its dependencies.