Ext Ops Panel
Open dashboard
Comparison

orion-trading-intelligence vs io.github.shemshallah/qtcl-mcp-server

orion-trading-intelligence is a plugin bundle for AI coding tools published by kokoju007. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.shemshallah/qtcl-mcp-server is an MCP server published by shemshallah. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplaceorion-trading-intelligenceio.github.shemshallah/qtcl-mcp-server
Claude Code: claude-plugins-community Listed
Version: f439281
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 8.2.0
Forks (GitHub): 0 (last published figure)
Stars (GitHub): 0 (last published figure)
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

orion-trading-intelligence vs io.github.shemshallah/qtcl-mcp-server
Factorion-trading-intelligenceio.github.shemshallah/qtcl-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0 (last published figure)
Forks (GitHub) (differs)No figure on GitHub0 (last published figure)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (qtcl-blockchain.koyeb.app/mcp/sse)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/kokoju007/orion-trading-plugingithub.com/shemshallah/qtcl-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 30 h ago returned HTTP 404

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

orion-trading-intelligence

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

BTC signals, ACP service monitoring, on-chain oracle for Claude Cowork. By cognac(꼬냑)

io.github.shemshallah/qtcl-mcp-server

In its own words, on Official MCP Registry:

Agent-native post-quantum blockchain. 11 tools: send, balance, quantum oracle metrics. Flat fee.

How to run each

orion-trading-intelligence As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install orion-trading-intelligence@claude-community

io.github.shemshallah/qtcl-mcp-server As a remote MCP server

Claude Code
claude mcp add --transport sse qtcl-mcp-server https://qtcl-blockchain.koyeb.app/mcp/sse

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

Only io.github.shemshallah/qtcl-mcp-server 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: orion-trading-intelligence · What it can do: io.github.shemshallah/qtcl-mcp-server · 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. 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