Ext Ops Panel
Open dashboard
Comparison

revolut-x vs SBOR

revolut-x is a plugin bundle for AI coding tools published by revolut-engineering. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SBOR is an MCP server published by sbor.xyz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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
Marketplacerevolut-xSBOR
Claude Code: claude-plugins-community Listed
Version: 1.0.47
Forks (GitHub): 19
Stars (GitHub): 74
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0
Downloads/month (npm): 1 768
Downloads/week (npm): 214
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.3.0
Downloads/month (npm): 1 768
Downloads/week (npm): 214
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

revolut-x vs SBOR
Factrevolut-xSBOR
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)74 (better)0 (worse)
Forks (GitHub) (differs)19 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
LicenceMITMIT
Repository (differs)github.com/revolut-engineering/revolut-x-apigithub.com/sborxyz/sbor
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-25

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

revolut-x

In its own words, on Claude Code: claude-plugins-community:

Trade crypto, query account state, stream market data, run live indicator alerts, and operate grid bots on the Revolut X exchange. Placing orders, checking balances, watching RSI/EMA/MACD, backtesting grid strategies.

SBOR

In its own words, on Official MCP Registry:

Check a lending rate before your agent borrows. Bitcoin-backed dollar rates from contracts. No key.

How to run each

revolut-x As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install revolut-x@claude-community

SBOR As a remote MCP server

Claude Code
claude mcp add --transport http sbor https://mcp.sbor.xyz/mcp

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

Only SBOR has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of revolut-x nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: revolut-x · What it can do: SBOR · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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