io.github.daedalus/mcp-rpcbind vs MOVA MCP Connector
io.github.daedalus/mcp-rpcbind is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). MOVA MCP Connector is an MCP server published by mova-compact. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  io.github.daedalus/mcp-rpcbind | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 58 Downloads/week (PyPI): 18 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 No figure published 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 | io.github.daedalus/mcp-rpcbind | MOVA MCP Connector |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-rpcbind) | On your machine (ghcr.io/mova-compact/mova-mcp-connector:0.1.0) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/daedalus/mcp-rpcbind | github.com/mova-compact/mova-mcp-connector |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
io.github.daedalus/mcp-rpcbind
MCP server exposing rpcbind/RPC portmapper functionality
MOVA MCP Connector
Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.
How to run each
io.github.daedalus/mcp-rpcbind As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-rpcbind -- uvx mcp-rpcbindMOVA MCP Connector
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: MCP_DOOR_ACTOR_ID, MCP_DOOR_GATEWAY_KEY_ID, MCP_DOOR_GATEWAY_SHARED_SECRET (secret), MOVA_ADMIN_READ_TOKEN (secret), MOVA_PLATFORM_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 io.github.daedalus/mcp-rpcbind publish no settings it asks for, so we do not compare settings.
What it can do: io.github.daedalus/mcp-rpcbind · What it can do: MOVA MCP Connector · 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.