Percher vs io.github.sota-deploy/sota
Percher is an MCP server published by percher.app. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.sota-deploy/sota is an MCP server published by sota-deploy. 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
| Marketplace |  Percher |  io.github.sota-deploy/sota |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.0 Downloads/month (npm): 1 753 Downloads/week (npm): 267 Not marked · First seen |
Listed Version: 1.1.1 Downloads/month (npm): 194 Downloads/week (npm): 25 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
| Fact | Percher | io.github.sota-deploy/sota |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-24 | Not published |
| Where it runs (differs) | Remote server (mcp.percher.app/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/sota-deploy/mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 32 h ago | Responded 3 days ago |
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
Percher
MCP-native hosting: publish and operate AI-built web apps live at name.percher.run.
io.github.sota-deploy/sota
Deploy web apps via AI agents with sota.io. 9 tools for deploy, logs, env, and more.
How to run each
Percher As a remote MCP server
claude mcp add --transport http percher https://mcp.percher.app/mcpio.github.sota-deploy/sota As a local MCP server: npm package
claude mcp add --transport stdio sota -- npx -y @sota-io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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: Percher · What it can do: io.github.sota-deploy/sota · 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.