Ext Ops Panel
Open dashboard
Comparison

beacon vs app.onehaus/haus

beacon is a plugin bundle for AI coding tools published by Aaron Sachs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). app.onehaus/haus is an MCP server published by onehaus.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacebeaconapp.onehaus/haus
Community marketplace asachs01/beacon Listed
Version: 1.0.0
Forks (GitHub): 13
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0
No figure published
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

beacon vs app.onehaus/haus
Factbeaconapp.onehaus/haus
Marketplaces that list it11
Stars (GitHub) (differs)16No figure on GitHub
Forks (GitHub) (differs)13No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.onehaus.app)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)10Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/asachs01/beacongithub.com/im5tu/haus
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

beacon

In its own words, on Community GitHub marketplaces:

Beacon family dashboard — chores, calendar, meal plans, grocery lists, media, weather

app.onehaus/haus

In its own words, on Official MCP Registry:

OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.

How to run each

beacon As a Claude Code plugin

Claude Code
/plugin marketplace add asachs01/beacon
/plugin install beacon@beacon

app.onehaus/haus As a remote MCP server

Claude Code
claude mcp add --transport http haus https://mcp.onehaus.app

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

Only app.onehaus/haus 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

The marketplaces of app.onehaus/haus publish no settings it asks for, so we do not compare settings.

What it can do: beacon · What it can do: app.onehaus/haus · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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