registry / post-engineer-mcp / 1.34.0
post-engineer-mcp@1.34.0
Post Engineer MCP Server for AI pair programming and agentic workflows
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged analytics is opt-in via POSTHOG_API_KEY, documented in the README, and its event wrapper supplies only the tool name. The inspected entry point starts the MCP server when invoked directly and showed no unrelated automatic behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The server starts when invoked as its executable; analytics runs after a tool call only when POSTHOG_API_KEY is configured.
Impact
No unauthorized data collection, account action, or other malicious behavior was found in the inspected paths.
Mechanism
The server sends authenticated requests to the Post Engineer API. Optional PostHog tracking sends the tool name and fixed source/environment tags.
AI rationale
The flagged analytics is opt-in via POSTHOG_API_KEY, documented in the README, and its event wrapper supplies only the tool name. The inspected entry point starts the MCP server when invoked directly and showed no unrelated automatic behavior.
Network endpoints2
eu.i.posthog.compost-engineer.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The README describes PostHog telemetry as optional and says it is disabled without POSTHOG_API_KEY.
- Analytics uses the supplied POSTHOG_API_KEY and returns without initializing PostHog when the key is absent.
- The tracking wrapper emits an mcp_tool_called event with the tool name; the event uses a fixed distinct ID.
- The package starts its MCP server only when run as the main module.
Evidence against
- When enabled, analytics sends events to https://eu.i.posthog.com by default, with POSTHOG_HOST available for configuration.
- The server uses POST_ENGINEER_API_KEY to authenticate requests to the Post Engineer API.
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
Low
Ai Review Evidence
The README describes PostHog telemetry as optional and says it is disabled without POSTHOG_API_KEY.
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.34.0.
See all versions of post-engineer-mcp for other recorded verdicts.
- Review the evidence and your use of post-engineer-mcp@1.34.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.