Vegas Mobile Mech — book mobile mechanic in Las Vegas vs elisym
Vegas Mobile Mech — book mobile mechanic in Las Vegas is an MCP server published by vegasmobilemech.com. Marketplaces we read that list it: 1 (Official MCP Registry). elisym is an MCP server published by elisymlabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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 |  Vegas Mobile Mech — book mobile mechanic in Las Vegas |  elisym |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.34.1 Downloads/month (npm): 1 638 Downloads/week (npm): 163 Forks (GitHub): 3 Stars (GitHub): 19 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.34.1 Downloads/month (npm): 1 638 Downloads/week (npm): 163 Forks (GitHub): 3 Stars (GitHub): 19 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 | Vegas Mobile Mech — book mobile mechanic in Las Vegas | elisym |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 19 |
| Forks (GitHub) (differs) | No figure on GitHub | 3 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Remote server (vegasmobilemech.com/mcp) | On your machine (@elisym/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/elisymlabs/elisym |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 10 h 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
Vegas Mobile Mech — book mobile mechanic in Las Vegas
Book mobile mechanic in Las Vegas, NV: prices, service area by ZIP, free callback from a local pro.
elisym
AI agent discovery, marketplace, messaging, and payments on Nostr - no platform, no middleman
How to run each
Vegas Mobile Mech — book mobile mechanic in Las Vegas As a remote MCP server
claude mcp add --transport http booking https://vegasmobilemech.com/mcpelisym As a local MCP server: npm package
claude mcp add --env "ELISYM_NOSTR_SECRET=<YOUR_ELISYM_NOSTR_SECRET>" --env "ELISYM_PASSPHRASE=<YOUR_ELISYM_PASSPHRASE>" --transport stdio elisym -- npx -y @elisym/mcpRequires: ELISYM_NOSTR_SECRET (secret), ELISYM_PASSPHRASE (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vegas Mobile Mech — book mobile mechanic in Las Vegas 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 Vegas Mobile Mech — book mobile mechanic in Las Vegas publish no settings it asks for, so we do not compare settings.
What it can do: Vegas Mobile Mech — book mobile mechanic in Las Vegas · What it can do: elisym · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.