Ext Ops Panel
Open dashboard
Comparison

KrystalView Analytics vs Pulse

KrystalView Analytics is an MCP server published by KrystalView. Marketplaces we read that list it: 1 (Official MCP Registry). Pulse is an MCP server published by pulsecircle.studio. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceKrystalView AnalyticsPulse
Official MCP Registry Listed
Version: 0.1.6
Downloads/month (PyPI): 252
Downloads/week (PyPI): 36
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 155
Downloads/week (npm): 27
Forks (GitHub): 0
Stars (GitHub): 0
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

KrystalView Analytics vs Pulse
FactKrystalView AnalyticsPulse
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server or your machineRemote server (mcp.pulse.pulsecircle.studio/mcp)
Transport (differs)Streamable HTTP, stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/krystalview/krystalview-mcpgithub.com/pulse-circle-studio/pulse-sdk
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agoNot responding since 2026-10-24

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

KrystalView Analytics

In its own words, on Official MCP Registry:

Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.

Pulse

In its own words, on Official MCP Registry:

Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only.

How to run each

KrystalView Analytics As a remote MCP server

Claude Code
claude mcp add --transport http krystalview https://krystalview.com/mcp

Requires: KRYSTALVIEW_API_KEY (secret)

Pulse As a remote MCP server

Claude Code
claude mcp add --transport http pulse https://mcp.pulse.pulsecircle.studio/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only the endpoint of KrystalView Analytics responded at the last daily 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

The marketplaces of Pulse publish no settings it asks for, so we do not compare settings.

What it can do: KrystalView Analytics · What it can do: Pulse · 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