Rube vs SRS Lock-in Amplifier
Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). SRS Lock-in Amplifier is an MCP server published by K-Dense-AI. 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 |  Rube |  SRS Lock-in Amplifier |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.3 Downloads/month (PyPI): 512 Downloads/week (PyPI): 38 Forks (GitHub): 2 Stars (GitHub): 22 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 | Rube | SRS Lock-in Amplifier |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 22 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (rube.app/mcp) | On your machine (labmcp-srs-lockin) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/k-dense-ai/lab-instrument-mcps |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-14 | 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
Rube
Access to Rube's catalog of remote MCP servers.
SRS Lock-in Amplifier
MCP server for Stanford Research Systems lock-in amplifiers (SR810/SR830, SR860/SR865A).
How to run each
Rube As a remote MCP server
claude mcp add --transport http rube https://rube.app/mcpRequires: RUBE_API_KEY (secret)
SRS Lock-in Amplifier As a local MCP server: PyPI package
claude mcp add --transport stdio labmcp-srs-lockin -- uvx labmcp-srs-lockinCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Rube 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
Only Rube asks for
RUBE_API_KEY (secret)
Only SRS Lock-in Amplifier asks for
LABMCP_ADDRESSLABMCP_LIMITSLABMCP_READ_ONLYLABMCP_SIMULATE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Rube · What it can do: SRS Lock-in Amplifier · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.