Gloam vs Obolus
Gloam is an MCP server published by cryptoduke01. Marketplaces we read that list it: 1 (Official MCP Registry). Obolus is an MCP server published by inviti8. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  Gloam |  Obolus |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Downloads/month (npm): 67 Downloads/week (npm): 67 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.3 Downloads/month (PyPI): 116 Downloads/week (PyPI): 32 Forks (GitHub): 0 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
| Fact | Gloam | Obolus |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.gloam.trade/mcp) | On your machine (obolus) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 2, secrets among them: 0 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/cryptoduke01/gloam | github.com/inviti8/obolus |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 43 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
Gloam
Private stablecoin payments for people and AI agents, hosted or local with spending limits.
Obolus
Disposable Algorand wallet for AI agents. Pay x402 resources in USDC, no human provisioning.
How to run each
Gloam As a remote MCP server
claude mcp add --transport http gloam https://www.gloam.trade/mcpRequires: GLOAM_AGENT_PRIVATE_KEY (secret), GLOAM_NOTE_KEY (secret)
Obolus As a local MCP server: PyPI package
claude mcp add --transport stdio obolus -- uvx obolus mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Gloam 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 Gloam asks for
GLOAM_AGENT_PRIVATE_KEY (secret)GLOAM_NOTE_KEY (secret)GLOAM_TEMPO_ACCOUNT
Only Obolus asks for
OBOLUS_DATA_DIROBOLUS_NETWORK
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Gloam · What it can do: Obolus · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.