Ext Ops Panel
Open dashboard
Comparison

io.github.OzorOwn/frostbyte vs io.github.swerve-hoe/ozma

io.github.OzorOwn/frostbyte is an MCP server published by OzorOwn. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.swerve-hoe/ozma is an MCP server published by swerve-hoe. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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.OzorOwn/frostbyteio.github.swerve-hoe/ozma
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.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

io.github.OzorOwn/frostbyte vs io.github.swerve-hoe/ozma
Factio.github.OzorOwn/frostbyteio.github.swerve-hoe/ozma
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/ozorown/frostbyte-mcp:latest)Remote server (mcp.ozma.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/ozorown/frostbyte-mcpgithub.com/swerve-hoe/ozma
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-15

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.OzorOwn/frostbyte

In its own words, on Official MCP Registry:

MCP server giving AI agents access to 40+ APIs: geo, crypto, screenshots, DNS, and more

io.github.swerve-hoe/ozma

In its own words, on Official MCP Registry:

Agentic API marketplace — search, provision, and call data sources with one Ozma key

How to run each

io.github.OzorOwn/frostbyte As a local MCP server: Docker image

Claude Code
claude mcp add --env "FROSTBYTE_API_KEY=<YOUR_FROSTBYTE_API_KEY>" --transport stdio frostbyte -- docker run -i --rm -e FROSTBYTE_API_KEY ghcr.io/ozorown/frostbyte-mcp:latest

Requires: FROSTBYTE_API_KEY (secret)

io.github.swerve-hoe/ozma As a remote MCP server

Claude Code
claude mcp add --transport http ozma https://mcp.ozma.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only io.github.swerve-hoe/ozma 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 io.github.swerve-hoe/ozma publish no settings it asks for, so we do not compare settings.

What it can do: io.github.OzorOwn/frostbyte · What it can do: io.github.swerve-hoe/ozma · Compare two other plugins

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