emisar vs Linux MCP daemon (mcpd)
emisar is an MCP server published by emisar.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Linux MCP daemon (mcpd) is an MCP server published by nucleusv. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |   emisar |  Linux MCP daemon (mcpd) |
|---|---|---|
| Official MCP Registry | Listed Version: 0.53.0 Forks (GitHub): 33 Stars (GitHub): 337 Not marked · First seen |
Listed Version: 0.5.1 Forks (GitHub): 1 Stars (GitHub): 6 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 | emisar | Linux MCP daemon (mcpd) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 337 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 33 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (emisar.dev/api/mcp/rpc) | Not stated |
| Transport (differs) | Streamable HTTP | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/andrewdryga/emisar | github.com/nucleusv/linux-mcp-daemon |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 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
emisar
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Linux MCP daemon (mcpd)
AI agent access to Linux servers without SSH: scoped tools, per-call isolation, root only if granted
How to run each
emisar As a remote MCP server
claude mcp add --transport http emisar https://emisar.dev/api/mcp/rpcLinux MCP daemon (mcpd)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only emisar 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: emisar · What it can do: Linux MCP daemon (mcpd) · 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.