Ext Ops Panel
Open dashboard
Comparison

LSEG vs Carry Intel — Hyperliquid funding screens

LSEG is a plugin bundle for AI coding tools published by LSEG-API-Samples. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Carry Intel — Hyperliquid funding screens is an MCP server published by TheArkofTech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceLSEGCarry Intel — Hyperliquid funding screens
Claude: knowledge-work-plugins Listed
Version: 1.0.0
Forks (GitHub): 4
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
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

LSEG vs Carry Intel — Hyperliquid funding screens
FactLSEGCarry Intel — Hyperliquid funding screens
Marketplaces that list it11
Stars (GitHub) (differs)120 (last published figure)
Forks (GitHub) (differs)40 (last published figure)
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (api.analytics.lseg.com/lfa/mcp)Remote server (devbox.tail873466.ts.net/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)17Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/lseg-api-samples/lseg-claude-plugingithub.com/thearkoftech/x402-carry-api
Changes in the last 7 days (differs)09
First seen (differs)2026-10-112026-10-12
Endpoint at the last checknot checked yetnot checked yet

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

LSEG

In its own words, on Claude: knowledge-work-plugins:

Price bonds, analyze yield curves, evaluate FX carry trades, value options, and build macro dashboards using LSEG financial data and analytics.

Carry Intel — Hyperliquid funding screens

In its own words, on Official MCP Registry:

Read-only Hyperliquid funding screens via x402 v2/Solana; not positions or returns.

How to run each

LSEG As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install lseg@knowledge-work-plugins

Carry Intel — Hyperliquid funding screens As a remote MCP server

Claude Code
claude mcp add --transport http carry-intel https://devbox.tail873466.ts.net:10000/mcp

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

Only Carry Intel — Hyperliquid funding screens 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: LSEG · What it can do: Carry Intel — Hyperliquid funding screens · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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