Ext Ops Panel
Open dashboard
Comparison

CloudSprite vs io.github.malkreide/meteoswiss-mcp

CloudSprite is an MCP server published by cloudsprite-io. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.malkreide/meteoswiss-mcp is an MCP server published by malkreide. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceCloudSpriteio.github.malkreide/meteoswiss-mcp
Official MCP Registry Listed
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.7.0
Downloads/month (PyPI): 305
Downloads/week (PyPI): 78
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

CloudSprite vs io.github.malkreide/meteoswiss-mcp
FactCloudSpriteio.github.malkreide/meteoswiss-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.cloudsprite.io/mcp)On your machine (meteoswiss-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/cloudsprite-io/cloudsprite-plugingithub.com/malkreide/meteoswiss-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 43 h ago, requires a keyno remote endpoint we check

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

CloudSprite

In its own words, on Official MCP Registry:

Signed-in CloudSprite: search datasets and docs, set org/team/project scope, file feedback.

io.github.malkreide/meteoswiss-mcp

In its own words, on Official MCP Registry:

MeteoSwiss Open Data for weather, climate normals, warnings

How to run each

CloudSprite As a remote MCP server

Claude Code
claude mcp add --transport http cloudsprite https://api.cloudsprite.io/mcp

io.github.malkreide/meteoswiss-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio meteoswiss-mcp -- uvx meteoswiss-mcp

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

Only CloudSprite 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

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

What it can do: CloudSprite · What it can do: io.github.malkreide/meteoswiss-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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