Ext Ops Panel
Open dashboard
Comparison

io.github.davidmosiah/eight-sleep-mcp vs Operto MCP by usefulapi

io.github.davidmosiah/eight-sleep-mcp is an MCP server published by davidmosiah. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Operto MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplaceio.github.davidmosiah/eight-sleep-mcpOperto MCP by usefulapi
Official MCP Registry Listed
Version: 0.2.5
Downloads/month (npm): 580
Downloads/week (npm): 138
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 1.6.5
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.2.13
Downloads/month (npm): 580
Downloads/week (npm): 138
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed

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

io.github.davidmosiah/eight-sleep-mcp vs Operto MCP by usefulapi
Factio.github.davidmosiah/eight-sleep-mcpOperto MCP by usefulapi
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-11-07
Where it runs (differs)On your machine (eight-sleep-mcp-unofficial)Remote server (operto.usefulapi.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 2Not published
Licence (differs)MITNot stated
Repository (differs)github.com/davidmosiah/eight-sleep-mcpgithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)012
First seen (differs)2026-10-112026-10-31
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 47 h ago returned HTTP 401

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

io.github.davidmosiah/eight-sleep-mcp

In its own words, on Official MCP Registry:

Unofficial Eight Sleep MCP server: read sleep trends, temperature, alarms; gated pod control.

Operto MCP by usefulapi

In its own words, on Official MCP Registry:

Read properties, reservations, guest access codes, smart locks and thermostats in Operto.

How to run each

io.github.davidmosiah/eight-sleep-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "EIGHT_SLEEP_CLIENT_SECRET=<YOUR_EIGHT_SLEEP_CLIENT_SECRET>" --env "EIGHT_SLEEP_PASSWORD=<YOUR_EIGHT_SLEEP_PASSWORD>" --transport stdio eight-sleep-mcp -- npx -y eight-sleep-mcp-unofficial

Requires: EIGHT_SLEEP_CLIENT_SECRET (secret), EIGHT_SLEEP_PASSWORD (secret)

Operto MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http operto https://operto.usefulapi.io/mcp

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

Only Operto MCP by usefulapi 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 Operto MCP by usefulapi publish no settings it asks for, so we do not compare settings.

What it can do: io.github.davidmosiah/eight-sleep-mcp · What it can do: Operto MCP by usefulapi · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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