Ext Ops Panel
Open dashboard
Comparison

spc-tools vs SpikeMe

spc-tools is a plugin bundle for AI coding tools published by ewolters. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SpikeMe is an MCP server published by isaacviannadev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplacespc-toolsSpikeMe
Claude Code: claude-plugins-community Listed
Version: 2d28422
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.6
Downloads/month (npm): 183
Downloads/week (npm): 58
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

spc-tools vs SpikeMe
Factspc-toolsSpikeMe
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (spikeme-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/ewolters/spc-toolsgithub.com/isaacviannadev/package-spike
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

spc-tools

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

SPC Tools gives Claude a calibrated, comprehensive statistical process control toolkit with pure-JavaScript visualization. Covers standard techniques (control charts, Cpk, Gage R&R) as well as Bayesian and distribution-free methods. No dependencies required; computation is pure Python, charts are zero-dependency ChartSpec JSON rendered client-side.

SpikeMe

In its own words, on Official MCP Registry:

Analyze your repo's stack and generate grounded, time-boxed spike decision docs.

How to run each

spc-tools As a Claude Code plugin

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

SpikeMe As a local MCP server: npm package

Claude Code
claude mcp add --env "SPIKEME_TOKEN=<YOUR_SPIKEME_TOKEN>" --transport stdio spikeme -- npx -y spikeme-mcp

Requires: SPIKEME_TOKEN (secret)

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

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 spc-tools publish no settings it asks for, so we do not compare settings.

What it can do: spc-tools · What it can do: SpikeMe · 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