Ext Ops Panel
Open dashboard
Comparison

LSEG vs J-Quants MCP

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). J-Quants MCP is an MCP server published by shigechika. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-28. 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
MarketplaceLSEGJ-Quants MCP
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.5.2
Downloads/month (PyPI): 517
Downloads/week (PyPI): 435
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.5.2
Downloads/month (PyPI): 517
Downloads/week (PyPI): 435
Forks (GitHub): 2
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

LSEG vs J-Quants MCP
FactLSEGJ-Quants MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)12 (better)3 (worse)
Forks (GitHub) (differs)4 (better)2 (worse)
Last release (differs)Not published2026-10-27
Where it runs (differs)Remote server (api.analytics.lseg.com/lfa/mcp)On your machine (jquants-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)17Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/lseg-api-samples/lseg-claude-plugingithub.com/shigechika/jquants-mcp
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno 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

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.

J-Quants MCP

In its own words, on Official MCP Registry:

MCP server for retrieving Japanese stock market data via J-Quants API v2

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

J-Quants MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio jquants-mcp -- uvx jquants-mcp

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

Only LSEG 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: J-Quants MCP · 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. Package data comes from the Python Package Index (pypi.org). 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.

Where the data comes from: how the catalog is built