Ext Ops Panel
Open dashboard
Comparison

AgentFirstStack Analytics vs com.mcparmory/posthog

AgentFirstStack Analytics is an MCP server published by agentfirststack.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.mcparmory/posthog is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAgentFirstStack Analyticscom.mcparmory/posthog
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.5
Downloads/month (PyPI): 830
Downloads/week (PyPI): 147
Forks (GitHub): 4
Stars (GitHub): 32
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

AgentFirstStack Analytics vs com.mcparmory/posthog
FactAgentFirstStack Analyticscom.mcparmory/posthog
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)32 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)2026-11-04Not published
Where it runs (differs)Remote server (analytics.agentfirststack.com/mcp)On your machine (mcparmory-posthog)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/startglobal-ai/agentfirststackgithub.com/mcparmory/registry
Changes in the last 7 days (differs)40
First seen (differs)2026-11-042026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AgentFirstStack Analytics

In its own words, on Official MCP Registry:

Cookieless web analytics an agent creates and queries: goals, funnels, revenue, SQL. Open source.

com.mcparmory/posthog

In its own words, on Official MCP Registry:

Capture analytics events, evaluate feature flags, and manage projects

How to run each

AgentFirstStack Analytics As a remote MCP server

Claude Code
claude mcp add --transport http analytics https://analytics.agentfirststack.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

com.mcparmory/posthog As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio posthog -- uvx mcparmory-posthog

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AgentFirstStack Analytics has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AgentFirstStack Analytics · What it can do: com.mcparmory/posthog · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built