Ext Ops Panel
Open dashboard
Comparison

halliday-payments vs io.github.codespar/mcp-celcoin

halliday-payments is a plugin bundle for AI coding tools published by HallidayInc. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.codespar/mcp-celcoin is an MCP server published by codespar. 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
Marketplacehalliday-paymentsio.github.codespar/mcp-celcoin
Claude Code: claude-plugins-community Listed
Version: 1.0.10
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.4
Downloads/month (npm): 418
Downloads/week (npm): 50
Forks (GitHub): 50
Stars (GitHub): 272
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

halliday-payments vs io.github.codespar/mcp-celcoin
Facthalliday-paymentsio.github.codespar/mcp-celcoin
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)272 (better)
Forks (GitHub) (differs)0 (worse)50 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@codespar/mcp-celcoin)
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)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/hallidayinc/hallidayclaudeplugingithub.com/codespar/mcp-dev-latam
Changes in the last 7 days00
First seen2026-10-112026-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

halliday-payments

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

A Clade Code plugin for development with Halliday Payments, the all-in-one platform for integrating crypto deposits, fiat-to-crypto onramps, and cross-chain swaps.

io.github.codespar/mcp-celcoin

In its own words, on Official MCP Registry:

MCP server for Celcoin — Pix, boleto, transfers, bill payments, top-ups

How to run each

halliday-payments As a Claude Code plugin

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

io.github.codespar/mcp-celcoin As a local MCP server: npm package

Claude Code
claude mcp add --env "CELCOIN_CLIENT_SECRET=<YOUR_CELCOIN_CLIENT_SECRET>" --transport stdio mcp-celcoin -- npx -y @codespar/mcp-celcoin

Requires: CELCOIN_CLIENT_SECRET (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 halliday-payments publish no settings it asks for, so we do not compare settings.

What it can do: halliday-payments · What it can do: io.github.codespar/mcp-celcoin · 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