registry / post-engineer-mcp / 1.38.0
post-engineer-mcp@1.38.0
Post Engineer MCP Server for AI pair programming and agentic workflows
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package's telemetry is documented as optional and disabled unless POSTHOG_API_KEY is set; the reviewed event contains only the tool name and a fixed package identifier. Its API key is used for the package's own service, and no malicious behavior was found in the reviewed entry points or flagged files.
Static reason
One or more suspicious static signals were detected.
Trigger
Product API calls occur when the user invokes MCP tools; analytics occurs on tool invocation only when POSTHOG_API_KEY is configured.
Impact
No malicious impact identified. The reviewed telemetry does not send tool arguments or credentials.
Mechanism
The client sends feature requests to https://post-engineer.com. Configured analytics sends the tool name and a fixed package identifier to PostHog.
AI rationale
The package's telemetry is documented as optional and disabled unless POSTHOG_API_KEY is set; the reviewed event contains only the tool name and a fixed package identifier. Its API key is used for the package's own service, and no malicious behavior was found in the reviewed entry points or flagged files.
Network endpoints3
post-engineer.comeu.i.posthog.comPOSTHOG_HOST (optional configurable PostHog host)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package documents telemetry as optional; without POSTHOG_API_KEY, it runs with telemetry disabled.
- Telemetry is sent when an MCP tool is invoked and records the tool name with a fixed package distinct ID.
- The manifest points to dist/index.js as its main and executable entry; its lifecycle scripts are build and test related, with no install hook.
- The API client uses the package's own service at https://post-engineer.com.
Evidence against
- When configured, the package sends tool invocation analytics to PostHog at https://eu.i.posthog.com by default.
- The server reads POST_ENGINEER_API_KEY from the environment for its own service requests.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsTelemetryUrlStrings
NoLicense
Source & flagged code
2 flaggeddist/analytics.jsView file
61package = post-engineer-mcp; repositoryIdentity = post-engineer; dependency = posthog-node
L61: // wants >=20.20 — on older Node this catch degrades to disabled.
L62: const { PostHog } = await import('posthog-node');
L63: const host = process.env['POSTHOG_HOST'] ?? DEFAULT_POSTHOG_HOST;
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/analytics.jsView on unpkg · L61README.mdView file
31### Telemetry (optional)
Set `POSTHOG_API_KEY` (and optionally `POSTHOG_HOST`, defaults to
`DEFAULT_POSTHOG_HOST` in `src/analytics.ts` — change the constant to
self-host) to send `mcp_tool_called` analytics events to
PostHog. Without it, the server runs normally with telemetry disabled.
The key is read from the environment only — never hardco
Low
Ai Review Evidence
The package documents telemetry as optional; without POSTHOG_API_KEY, it runs with telemetry disabled.
README.mdView on unpkg · L31Findings
1 High3 Medium8 Low
HighCopied Package Dependency Bridgedist/analytics.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
LowAi Review EvidenceREADME.md
Affected versions and remediation
This report applies to post-engineer-mcp@1.38.0.
See all versions of post-engineer-mcp for other recorded verdicts.
- Review the evidence and your use of post-engineer-mcp@1.38.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.