Ext Ops Panel
Open dashboard
Comparison

voltaire vs io.github.docracy1/monthsleft

voltaire is a plugin bundle for AI coding tools published by voltairehq. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.docracy1/monthsleft is an MCP server published by docracy1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacevoltaireio.github.docracy1/monthsleft
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

voltaire vs io.github.docracy1/monthsleft
Factvoltaireio.github.docracy1/monthsleft
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.hivoltaire.com/mcp)Remote server (monthsleft.netlify.app/.netlify/functions/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/voltairehq/voltaire-plugingithub.com/docracy1/monthsleft
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-14Responded 18 h ago

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

voltaire

In its own words, on Claude Code: claude-plugins-community:

Revenue intelligence for SaaS paywall conversion. Voltaire connects Stripe data, installs behavioral tracking into the codebase, and runs three AI agents on every /voltaire: timing analysis, cohort comparison, and churn tracking to surface where conversion is being lost and what to fix.

io.github.docracy1/monthsleft

In its own words, on Official MCP Registry:

SaaS runway calculator (MRR growth vs churn), breakeven, burn multiple. Free MCP connector.

How to run each

voltaire As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install voltaire@claude-community

io.github.docracy1/monthsleft As a remote MCP server

Claude Code
claude mcp add --transport http monthsleft https://monthsleft.netlify.app/.netlify/functions/mcp

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

Only the endpoint of io.github.docracy1/monthsleft 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

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

What it can do: voltaire · What it can do: io.github.docracy1/monthsleft · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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