registry / post-engineer-mcp / 1.35.0
post-engineer-mcp@1.35.0
Post Engineer MCP Server for AI pair programming and agentic workflows
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged analytics code is gated on an explicitly supplied PostHog key and records only tool names. The package’s API key is sent to its own HTTPS service as part of the MCP tool functionality, and the manifest has no install hook.
Static reason
One or more suspicious static signals were detected.
Trigger
API requests occur when tools are invoked; analytics additionally requires POSTHOG_API_KEY to be set.
Impact
Package API operations and limited tool-usage metrics; no credential exfiltration or unrequested account action identified.
Mechanism
The client sends its API key to the package service. Analytics records the tool name and sends it to PostHog when configured.
AI rationale
The flagged analytics code is gated on an explicitly supplied PostHog key and records only tool names. The package’s API key is sent to its own HTTPS service as part of the MCP tool functionality, and the manifest has no install hook.
Network endpoints2
post-engineer.comeu.i.posthog.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has a prepublishOnly build script but no install lifecycle hook.
- Analytics initialization returns without sending events when POSTHOG_API_KEY is absent.
- Tool calls emit an event with the tool name and a fixed package distinct ID; no request arguments are included.
- The API client sends its API key to the package’s HTTPS service, post-engineer.com.
Evidence against
- When POSTHOG_API_KEY is set, tool-use events are sent to PostHog at https://eu.i.posthog.com.
- The package makes API requests when its tools are invoked.
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 · L61package.jsonView file
21"scripts": {
"build": "tsc -p tsconfig.json",
"prepublishOnly": "pnpm build",
"start": "node dist/index.js",
"test": "vitest run",
"test:watch": "vitest watch
Low
Suspicious Lifecycle Evidence
The manifest has a prepublishOnly build script but no install lifecycle hook.
package.jsonView on unpkg · L21Findings
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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to post-engineer-mcp@1.35.0.
See all versions of post-engineer-mcp for other recorded verdicts.
- Review the evidence and your use of post-engineer-mcp@1.35.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.