Ext Ops Panel
Open dashboard
Comparison

bemora vs Nomad Stays

bemora is an MCP server published by Demon-radio. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Nomad Stays is an MCP server published by nomadstays. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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

Where each is published
MarketplacebemoraNomad Stays
npm registry (MCP servers) Listed
Version: 1.0.0-alpha.13
Downloads/month (npm): 1 107
Downloads/week (npm): 117
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.0
Forks (GitHub): 1
Stars (GitHub): 0
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

bemora vs Nomad Stays
FactbemoraNomad Stays
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-11-04Not published
Where it runs (differs)On your machine (bemora)Remote server (mcp.nomadstays.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/demon-radio/bemora.lolgithub.com/nomadstays/nomadstays-mcp-server
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (6 h ago)

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

bemora

In its own words, on npm registry (MCP servers):

Unified API library for apps and AI agents — payments (Stripe, PayPal), email (SendGrid, SES, Resend), SMS (Twilio), auth (JWT, Clerk, Auth0), storage (S3, R2, GCS), vector DBs, AI providers (OpenAI, Anthropic, Gemini, Groq, & more), Cloudflare, and 100+

Nomad Stays

In its own words, on Official MCP Registry:

Search remote-work accommodations worldwide; Trusted Stay Partners can manage their own listings.

How to run each

bemora

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Nomad Stays As a remote MCP server

Claude Code
claude mcp add --transport http nomad-stays https://mcp.nomadstays.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Nomad Stays 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: bemora · What it can do: Nomad Stays · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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.

Where the data comes from: how the catalog is built