MCP100 IndexMCP Server
WatchlistFirst-party MCP

PostHog MCP

by PostHog

Reviewed October 5, 2026

MCP ServerSoftware & Technology

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to PostHog MCP analytics for tool usage and client identity across server pods: Do stateless session identifiers and sampling preserve correlation without exposing unnecessary client data?

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Instrumenting and operating PostHog-aware MCP services

What we know

Official PostHog package for MCP analytics instrumentation and stateless/multi-pod deployment support.

Maintenance / activity evidence

  • @posthog/mcp 0.22.0 published 2026-10-05T13:05:57.812Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Depends on PostHog/project integration. Writes: Event/telemetry ingestion; exact MCP tool writes unresolved.
  • Authentication not yet verified.
  • Sensitive access: Analytics/event data
  • Treat instrumentation payloads as potentially sensitive; verify exact project token/auth behavior before enabling broadly.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 773.2k package downloads / 30 days

Downloads observed Sep 25, 2026.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

All limitations / Review context

Do stateless session identifiers and sampling preserve correlation without exposing unnecessary client data?

The bounded review of the publisher's documented PostHog MCP analytics for tool usage and client identity across server pods and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

  • Treat instrumentation payloads as potentially sensitive; verify exact project token/auth behavior before enabling broadly.
  • Depends on PostHog/project integration.
  • MCP analytics/event data may be sent to PostHog.
  • Reviewed write actions: Event/telemetry ingestion; exact MCP tool writes unresolved
  • Sensitive access: Analytics/event data
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
  • Documented tool authority and any remote data handling must be checked before installation or use.
  • Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
  • Repository identity
  • Exact tool/auth model
  • Cost
  • The package page did not establish the complete tool/auth surface in this audit.

Original activity observations

  • @posthog/mcp 0.22.0 published 2026-10-05T13:05:57.812Z
Technical identity
npm/@posthog/mcp
Reviewed resource type
MCP Server
Package identity
@posthog/mcp

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation

  • Package registry ↗

    @posthog/mcp

    Recorded package identity, distribution or download evidence.

    Includes references whose attribution is not established.

  • Repository document ↗

    posthog/posthog-js

    Recorded repository material and project history.