CloudScale-Sim vs Signadot MCP Server
CloudScale-Sim is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). Signadot MCP Server is an MCP server published by signadot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  Signadot MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: v1.9.0 Forks (GitHub): 5 Stars (GitHub): 8 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
| Fact | CloudScale-Sim | Signadot MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 8 |
| Forks (GitHub) (differs) | No figure on GitHub | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (cloudscale-sim-mcp.vercel.app/api/mcp) | On your machine (https://github.com/signadot/cli/releases/download/v1.9.0/signadot-cli_mcp_linux_amd64.tar.gz) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/signadot/cli |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (2 days ago) | no 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
CloudScale-Sim
Cloud infrastructure auto-scaling load test simulator.
Signadot MCP Server
Connect to Signadot to manage ephemeral environments and route traffic to local services.
How to run each
CloudScale-Sim As a remote MCP server
claude mcp add --transport sse cloudscale-sim https://cloudscale-sim-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Signadot MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: SIGNADOT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only CloudScale-Sim 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 CloudScale-Sim publish no settings it asks for, so we do not compare settings.
What it can do: CloudScale-Sim · What it can do: Signadot MCP Server · 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.