Ext Ops Panel
Open dashboard
Comparison

@bilig/headless vs @retiregolden/mcp

@bilig/headless is an MCP server published by @bilig. Marketplaces we read that list it: 1 (npm registry (MCP servers)). @retiregolden/mcp is an MCP server published by RetireGolden. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplace@bilig/headless@retiregolden/mcp
npm registry (MCP servers) Listed
Version: 0.164.11
Downloads/month (npm): 59 801
Downloads/week (npm): 7 723
Forks (GitHub): 18
Stars (GitHub): 35
Not marked · First seen
Listed
Version: 0.13.1
Downloads/month (npm): 915
Downloads/week (npm): 761
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

@bilig/headless vs @retiregolden/mcp
Fact@bilig/headless@retiregolden/mcp
Marketplaces that list it11
Stars (GitHub) (differs)35 (better)0 (worse)
Forks (GitHub) (differs)18 (better)0 (worse)
Last release (differs)Not published2026-11-06
Where it runs (differs)On your machine (@bilig/headless)On your machine (@retiregolden/mcp)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITAGPL-3.0-only
Repository (differs)github.com/proompteng/biliggithub.com/retiregolden/retiregolden-mcp
Changes in the last 7 days (differs)01
First seen2026-10-122026-10-12

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

@bilig/headless

In its own words, on npm registry (MCP servers):

Lower-level WorkPaper formula runtime for Node services with JSON persistence and verified formula readback.

@retiregolden/mcp

In its own words, on npm registry (MCP servers):

Model Context Protocol server for the RetireGolden retirement-planning engine: headless, in-memory sessions over stdio (and optional HTTP).

How to run each

@bilig/headless

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

@retiregolden/mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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

What it can do: @bilig/headless · What it can do: @retiregolden/mcp · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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