Versus comparison
Claude Command Center vs Hol Registry
Developers who already run several coding agents and keep losing track of them in terminal tabs. CCC is worth a look if you launch Claude Code, Codex, Cursor and friends from a terminal and want one local board that shows every session, which one is waiting on you, and which has quietly run out of context - without routing your work through someone else's cloud. It is not a fit for a single-session user (a terminal is enough), for anyone who wants a hosted team product with accounts and permissions, for a Windows or Linux shop expecting parity with the macOS app, or for a buyer who needs a company entity and a governing-law clause before installing software. · discovering and comparing installable Claude Code, Codex, Cursor, and MCP plugins with publisher and trust signals
| Decision point | CCC (Claude Command Center) | HOL Registry |
|---|---|---|
| Best for | Developers who already run several coding agents and keep losing track of them in terminal tabs. CCC is worth a look if you launch Claude Code, Codex, Cursor and friends from a terminal and want one local board that shows every session, which one is waiting on you, and which has quietly run out of context - without routing your work through someone else's cloud. It is not a fit for a single-session user (a terminal is enough), for anyone who wants a hosted team product with accounts and permissions, for a Windows or Linux shop expecting parity with the macOS app, or for a buyer who needs a company entity and a governing-law clause before installing software. | discovering and comparing installable Claude Code, Codex, Cursor, and MCP plugins with publisher and trust signals |
| Category | Development | Development |
| Price | Free: USD 0, with no tiers, no paid plan, no seat count and no account for the local app. Licensed FSL-1.1-MIT (copyright 2026 Amir Fish), which is source-available rather than OSI open source: you may use, copy, modify and redistribute it for any Permitted Purpose, a Competing Use is barred, and each version converts to the MIT license on its second anniversary. Downloads are a 3.6 MB notarized and Apple-signed DMG, a Homebrew tap (amirfish1/tap/ccc), a curl installer for macOS/Linux and a PowerShell installer for Windows. The optional CCC Cloud phone relay is account-based; no price appears for it on any fetched page either. No page on the site carries a price token other than $0. | Free |
| AIToolsEssentials editorial score | 4.1/5 | 4.0/5 |
Scores are editorial product assessments — job fit, likely output quality, ease of adoption, and operational cost — not lab benchmarks, and no tool here has a published hands-on result. How we score.
Evidence status
Free. USD 0 with no tiers, no paid plan, no seat count, no trial clock and no account for the local app. Verified by sweeping every served page for price tokens: the homepage carries only '$0' (the free-model choice), and /captain/, /receipts/, /watchtower/, /vs-heavyweight-ides.html and /demo/ carry no price token at all. Check that the product is actually obtainable rather than merely announced: the release asset releases/latest/download/ccc.dmg answers HTTP 200 with content-type application/octet-stream and 3,614,187 bytes, and the Homebrew formula at raw.githubusercontent.com/amirfish1/homebrew-tap/main/Formula/ccc.rb answers 200. License is FSL-1.1-MIT, copyright 2026 Amir Fish: Permitted Purpose use including internal and professional use, no Competing Use, and an irrevocable grant of MIT on the second anniversary of each version's release. GitHub reports the license as NOASSERTION because FSL is not an SPDX-recognised open-source license, which matches the site's own description of itself as source-available. The optional CCC Cloud relay is account-based; its user guide lists no price, so there is no recurring figure to verify.
Official sources checked 2026-10-24submitted via form by vendor; editorial entry written independently. Received through FormSubmit on 2026-10-24 20:32 UTC with pricing_url and docs_url both pointing at the GitHub repository and contact_email amir.fish@gmail.com. No privacy_url is recorded because none exists: /privacy, /terms, /privacy.html, /terms.html and /legal/ all 404 on ccc.amirfish.ai, and the parent brand domain amirfish.ai returns 404 for /privacy, /terms, /privacy.html and /terms.html and publishes no sitemap. Product verified by fetching the live site and its subpages (/, /captain/, /receipts/, /watchtower/, /demo/, /vs-heavyweight-ides.html all 200), the repository metadata via the GitHub API (created 2026-04-13, 202 stars, 25 forks, 8 open issues, default branch main, license reported NOASSERTION, pushed the same day as this review) and the raw LICENSE, SECURITY.md, docs/telemetry.md and docs/cloud-relay/SECURITY-AND-PRIVACY.md. The telemetry claim was checked against source (ccc_server/fleet_jobs.py) rather than against the policy page: the payload and the never-sent list are documented in the module, the retired opt-in ping is described in the same comment, and the kill switch is an environment variable. Website analytics were read from the served /analytics.js: PostHog with persistence memory, person_profiles identified_only, and autocapture, pageleave, session replay, surveys, dead clicks, performance, heatmaps and exception capture all disabled, respect_dnt true. Operator identity is a named individual (Amir Fish, copyright holder in the LICENSE) with a personal site at amirfish.ai naming Sunnyvale, California and a LinkedIn profile, plus amir@amirfish.com published there and amir.fish@gmail.com in the submission; the domain amirfish.ai publishes MX (10 inbound-smtp.us-east-1.amazonaws.com), so a domain address is deliverable in principle, but no company entity, postal address or governing-law clause exists. Name collision checked: at least five unrelated GitHub repositories use the same 'claude-command-center' name (nubbymong, Dicoangelo, sorlen008, afstkla, adamclark64) and none is a live incumbent commercial product trading under CCC, so this is a crowded descriptive name rather than a rights dispute. Third-party coverage exists (a YouTube walkthrough, ai-underdog.com, reporank.net, marketgenius.ai, and an entry in andyrewlee/awesome-agent-orchestrators), so the product is not a single unverified page. No hands-on testing was performed: hands_on_status is not_tested and every workflow claim in the listing is attributed to the vendor's own documentation or to the shipped source.
Free. Browsing the plugin catalogue and submitting a public plugin repository cost nothing - stated in the catalogue's own FAQ ("list your public repository for free") and in the live https://hol.org/plugins/llms.txt, which sells nothing. No paid tier exists for the catalogue itself; paid credits apply to other HOL registry operations, and HOL Guard is a separately priced product with its own plans. Verified 2026-10-14 from the live /plugins/llms.txt plus the archived catalogue page, because live catalogue HTML is served behind a Cloudflare challenge and returned 403 to every scripted client.
Official sources checked 2026-10-14Open verification questions
- No general site-wide Terms of Service was located. The footer link labelled "Terms of Service" resolves to https://hol.org/points/legal/terms (a points-programme legal page) in both the live app shell and the archived pages, and that page's actual scope could not be read because live HTML is Cloudflare-challenged. Treat the recorded rights_url as the only terms link found, not as confirmed coverage of the catalogue.
- Catalogue size disagrees between HOL's own surfaces: the archived catalogue page (2026-08-31) read "Showing 243 plugins across 16 ecosystems" while the live /plugins/llms.txt says "205 catalog plugins". The listing therefore quotes no figure.
- Retention periods and named subprocessors are asserted in the privacy summary ("the complete policy names categories of providers and explains ... retention") but the full Privacy Policy, stated as last updated 2026-06-29, could not be read from this host. Retention and processor specifics are unverified.
- Security scoring is a fallback static catalogue scan, not a live exploit test - disclosed by the site itself in its FAQ and llms.txt. Any trust score should be read as a weak signal, and the listing's pros/cons say so.
- The privacy summary warns that information written to a public blockchain can be visible to third parties and may be permanent even after an off-chain account is deleted. This applies to HOL Points and registry features rather than the plugin catalogue, but is not itemised per product.
Submitted via the site form by the vendor (name "HOL Plugins", url https://hol.org/plugins, category Development, contact michael@hol.org) - FormSubmit mail timestamped Thu, 2026-10-15 00:22 UTC, i.e. 2026-10-14 in the site's Pacific working date. Editorial entry written independently; no vendor copy reused and no revenue figure inferred. Operator identity verified twice: (1) the site's own About and Contact pages state that "Hashgraph Online DAO LLC operates hol.org", give the business address 852 Long Island Rd, Majuro 96960, Marshall Islands, and publish +1 347-705-7394 and support@hol.org; (2) independently, the GitHub organisation "hashgraph-online" (display name "HOL (Hashgraph Online)", 66 public repositories, created 2024-02-18) lists hol.org as its blog, Marshall Islands as its location and support@hol.org as its email, and its hol-guard repository lists https://hol.org/guard as its homepage (Apache-2.0, 896 stars, last pushed 2026-10-15). Submitted contact michael@hol.org is a real mailbox: SMTP RCPT probe against the domain's own Google Workspace MX returned 250 2.1.5 OK, while a random local part returned 550 5.1.1, proving the domain is not a catch-all. Provenance limits, stated plainly: hol.org serves its HTML, its sitemap.xml, its OpenAPI document and its live API endpoints behind a Cloudflare challenge (403 to every scripted client; only the llms.txt surfaces load), and the interactive browser was unavailable on this host, so the catalogue, About, Contact and Privacy pages were read from Wayback snapshots (catalogue 2026-08-31; About 2026-09-19; Contact 2026-09-19; Privacy 2026-09-24) and cross-checked against the live surfaces that do load: /plugins/llms.txt, /guard/llms.txt, robots.txt and the live 404 app shell, which carries the site's full navigation. Ownership is not in question on any reading.
How to decide
Match each platform to your actual workflow constraints. Run one real workflow in each finalist before paying.
Quick recommendation
Use the trial checklist on each review page and the free scorecard to record time-to-result, corrections needed, and monthly cost at your expected volume before committing to a plan.
Read CCC (Claude Command Center) review Read HOL Registry review Open scorecard
Get a shareable decision brief for this matchup →
Free · no login · stays on your device
Free Stack Audit
See which AI subscriptions overlap and what you could cut before the next renewal.