Pmcp MCP Server

pmcp-server npm v2.1.0

Published by thana0623 — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
C
75/100
Last scanned
Trust
C · 75/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
C Why this grade 100 − 24.9 = 75/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−18.6 Near-miss of @sentry/mcp-server ×2 MTC-SUP-005 supply-chain
−6.3 Package runs install-time scripts MTC-SUP-010 supply-chain

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 the deduction.

Findings 5

high Shell/command execution in server code (build/git-utils.js)MTC-SRC-002

In the server's implementation (`build/git-utils.js:7`): 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: child_process

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 build/git-utils.js

high Shell/command execution in server code (build/publisher.js)MTC-SRC-002

In the server's implementation (`build/publisher.js:13`): 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: child_process

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 build/publisher.js

high Near-miss of @sentry/mcp-server (edit distance 1)MTC-SUP-005

"pmcp-server" is edit-distance 1 from the high-traffic package "@sentry/mcp-server". Verify this is the intended package.

Fix: Confirm you meant "@sentry/mcp-server". Install packages only from their documented, official name.

Location: package pmcp-server

medium Near-miss of @heroku/mcp-server (edit distance 1)MTC-SUP-005

"pmcp-server" is edit-distance 1 from the package "@heroku/mcp-server". Verify this is the intended package.

Fix: Confirm you meant "@heroku/mcp-server". Install packages only from their documented, official name.

Location: package pmcp-server

medium Package runs install-time scripts (postinstall)MTC-SUP-010

"pmcp-server" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package pmcp-server

What this scan could not see

Versions

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.

VersionScoreFindingsEngineScanned
v2.1.0 latest C 75/100 5 1.5.0 2026-07-22

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.

MCP Trust Score: C · 75/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pmcp-server/badge.svg)](https://mcptrustchecker.com/registry/pmcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/pmcp-server"><img src="https://mcptrustchecker.com/registry/pmcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pmcp-server/badge.json via https://img.shields.io/endpoint?url=…

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 pmcp-server --online

Use the free API → How scoring works

More in Developer Tools