Ext Ops Panel
Open dashboard
Comparison

numeric-mcp-toolkit vs io.github.Baneado98/muni-dev-cost

numeric-mcp-toolkit is a plugin bundle for AI coding tools published by geoff-lew. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Baneado98/muni-dev-cost is an MCP server published by Baneado98. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacenumeric-mcp-toolkitio.github.Baneado98/muni-dev-cost
Claude Code: claude-plugins-community Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.18.1
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

numeric-mcp-toolkit vs io.github.Baneado98/muni-dev-cost
Factnumeric-mcp-toolkitio.github.Baneado98/muni-dev-cost
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (muni-dev-cost-mcp.vercel.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)20Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/geoff-lew/numeric-toolkitgithub.com/baneado98/muni-dev-cost
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (30 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

numeric-mcp-toolkit

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

Skills for the Numeric's MCP. Purpose-built workflows for accounting teams — rec workbooks, department anomaly scanning, cross-workspace close dashboards, audit evidence exports, close pulse reporting, consolidated flux commentary, financial metrics, clean report exports, and executive/board-ready reports.

io.github.Baneado98/muni-dev-cost

In its own words, on Official MCP Registry:

US municipal development cost: aggregated impact + water/sewer tap fees per jurisdiction

How to run each

numeric-mcp-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install numeric-mcp-toolkit@claude-community

io.github.Baneado98/muni-dev-cost As a remote MCP server

Claude Code
claude mcp add --transport http muni-dev-cost https://muni-dev-cost-mcp.vercel.app/mcp

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

Only io.github.Baneado98/muni-dev-cost 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: numeric-mcp-toolkit · What it can do: io.github.Baneado98/muni-dev-cost · 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