Loomal Index vs mcp-get discovery and payments vs local install.
mcp-get is a command-line tool and directory for installing open-source MCP servers on your machine. Loomal Index covers local and remote servers alike, and adds the layer an installer can't: per-call x402 payments. A package manager and a marketplace are different things.
mcp-get answers a narrow, useful question: 'how do I get this open-source MCP server installed on my machine?' It's a CLI plus a directory, in the spirit of a package manager — find a server, run a command, it's configured locally.
Loomal Index answers a wider set of questions: what servers exist across the ecosystem (local and remote), what does calling one cost, and how does an agent pay for it. The comparison is short because the overlap is thin — but if you're deciding where your server should be findable, it's worth seeing clearly.
What mcp-get does well
mcp-get reduces installing an open-source MCP server to a single CLI command — discovery and setup in one tool. For a developer wiring local stdio servers into a client, that's a real friction cut compared with hand-editing config files and hunting package names across READMEs.
Its directory is also a legitimate browsing surface for the open-source corner of the ecosystem: free servers you run yourself, on your own machine.
Where the installer model stops
An installer's worldview is local: packages you download and run. That leaves out the growing population of remote MCP servers — hosted endpoints reached over streamable HTTP that you don't install at all. It also has nothing to say about money. The servers mcp-get installs are free software, which is great, but the model has no slot for a server whose calls cost something: no price field, no payment flow, no way for a maintainer to earn from usage.
None of that is a flaw in mcp-get — it's just a smaller job than the one a marketplace does.
What Loomal adds
Loomal Index spans both deployment shapes: locally-run packages and hosted remote servers appear as listings with metadata, connection details, and — when the owner claims the listing — x402 pricing. The payment layer is what changes the economics: an agent calling a priced endpoint gets an HTTP 402, pays in USDC on Base (settled in about two seconds, no chargebacks, Ed25519-signed receipts), and the handler runs after payment clears.
For maintainers, that's the difference between a download count and a revenue line. A server that's free to install via mcp-get can still offer a paid hosted endpoint listed on Loomal, priced from $0.01 per call — open source and per-call revenue aren't mutually exclusive.
Different consumers entirely
mcp-get serves a developer at a terminal setting up their own environment. Loomal serves two parties that tool doesn't: autonomous agents querying for capabilities programmatically at run time, and maintainers who want usage to pay them. A human installing a free local server has no need for a payment rail; an agent selecting a tool mid-task has no use for a CLI installer.
So 'versus' overstates it. The honest framing is that mcp-get covers install-time convenience for free local servers, and Loomal covers run-time discovery and monetization across the whole ecosystem.
When to use which
Reach for mcp-get when you're a developer setting up free, open-source servers on your own machine. Use Loomal when you need agents to discover your server, when you want to charge per call for a hosted endpoint, or when you're hunting for capabilities beyond the locally-installable open-source set. If you maintain a server distributed through mcp-get, claiming its Loomal listing costs nothing and adds the monetization path the installer can't provide.
FAQ
Is Loomal a replacement for mcp-get?
Not really — mcp-get is a CLI for installing free open-source MCP servers locally, while Loomal is a marketplace covering local and remote servers with x402 pay-per-call monetization. A developer might use mcp-get for setup and Loomal for discovery and revenue; the jobs barely overlap.
Does mcp-get support payments of any kind?
mcp-get's model is installing open-source servers onto your local machine, and the servers in its directory are free software you run yourself. There's no pricing or payment concept in an installer workflow — that's the layer Loomal adds with x402.
My server is free and open source. Why list it on Loomal?
Discovery, first: agents and developers querying Loomal find your server alongside the rest of the ecosystem. And optionally revenue: you can keep the package free while offering a paid hosted endpoint priced from $0.01 per call, so heavy programmatic users fund the project.
Does Loomal cover remote MCP servers that aren't installable packages?
Yes — that's a core difference. Hosted servers reached over streamable HTTP are first-class listings on Loomal, with the same claim and x402 pricing flow as package-based servers. Installer-style directories are limited to what runs locally.
More than a download.
Claim your server's listing and turn calls into revenue.