Flowsery vs com.tracklution/server-side-tracking
Flowsery is an MCP server published by flowsery.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.tracklution/server-side-tracking is an MCP server published by tracklution.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  Flowsery |  com.tracklution/server-side-tracking |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 No figure published Not marked · First seen |
Listed Version: 3.2.1 Downloads/month (npm): 326 Downloads/week (npm): 56 Forks (GitHub): 0 Stars (GitHub): 2 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
| Fact | Flowsery | com.tracklution/server-side-tracking |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (mcp.flowsery.com/mcp) | On your machine (tracklution) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/tracklution/tracklution-cli |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no 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
Flowsery
Web analytics for AI agents: realtime visitors, revenue, funnels and AI-detected site issues
com.tracklution/server-side-tracking
Server-side conversion tracking, installed and configured by your AI coding agent.
How to run each
Flowsery As a remote MCP server
claude mcp add --transport http flowsery https://mcp.flowsery.com/mcpcom.tracklution/server-side-tracking As a local MCP server: npm package
claude mcp add --transport stdio server-side-tracking -- npx -y tracklutionCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Flowsery 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: Flowsery · What it can do: com.tracklution/server-side-tracking · 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.