Ext Ops Panel
Open dashboard
Comparison

orion-trading-intelligence vs Pulse Verity

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). Pulse Verity is an MCP server published by PulseBet. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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-intelligencePulse Verity
Claude Code: claude-plugins-community Listed
Version: f439281
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.6
Downloads/month (npm): 1 370
Downloads/week (npm): 629
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.3.6
Downloads/month (npm): 1 370
Downloads/week (npm): 629
Forks (GitHub): 0
Stars (GitHub): 3
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 Pulse Verity
Factorion-trading-intelligencePulse Verity
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-19
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 for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/kokoju007/orion-trading-plugingithub.com/pulsebet/pulse-verity
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 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

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(꼬냑)

Pulse Verity

In its own words, on Official MCP Registry:

Signed Bitcoin and crypto prices for AI agents: multi-exchange prices anyone can verify offline.

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

Pulse Verity As a remote MCP server

Claude Code
claude mcp add --transport http pulse-verity https://mcp.thepulse.markets/api/index/mcp

Requires: PULSE_API_KEY (secret)

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

Only Pulse Verity has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of orion-trading-intelligence nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of orion-trading-intelligence publish no settings it asks for, so we do not compare settings.

What it can do: orion-trading-intelligence · What it can do: Pulse Verity · 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