in.termal/termalin-web vs Termix
in.termal/termalin-web is an MCP server published by termal.in. Marketplaces we read that list it: 1 (Official MCP Registry). Termix is an MCP server published by sujirodev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  in.termal/termalin-web |  Termix |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (PyPI): 149 Downloads/week (PyPI): 17 Forks (GitHub): 1 Stars (GitHub): 1 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 | in.termal/termalin-web | Termix |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (termal.in/api/v1/mcp) | On your machine (termix-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/sujirodev/termix-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 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
in.termal/termalin-web
Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP).
Termix
Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager)
How to run each
in.termal/termalin-web As a remote MCP server
claude mcp add --transport http termalin-web https://termal.in/api/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Termix As a local MCP server: PyPI package
claude mcp add --env "TERMIX_API_KEY=<YOUR_TERMIX_API_KEY>" --env "TERMIX_URL=<YOUR_TERMIX_URL>" --transport stdio termix-mcp -- uvx termix-mcpRequires: TERMIX_API_KEY (secret), TERMIX_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only in.termal/termalin-web 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 in.termal/termalin-web publish no settings it asks for, so we do not compare settings.
What it can do: in.termal/termalin-web · What it can do: Termix · 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.