LSEG vs Monte-Neo strategy verifier
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). Monte-Neo strategy verifier is an MCP server published by NeoZorK. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  LSEG |  Monte-Neo strategy verifier |
|---|---|---|
| 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: 0.54.0 Downloads/month (PyPI): 5 691 Downloads/week (PyPI): 396 Forks (GitHub): 0 Stars (GitHub): 8 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
| Fact | LSEG | Monte-Neo strategy verifier |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 (better) | 8 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (api.analytics.lseg.com/lfa/mcp) | On your machine (monte-neo) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/lseg-api-samples/lseg-claude-plugin | github.com/neozork/monte-neo |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 40 h ago, requires a key | no 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
Price bonds, analyze yield curves, evaluate FX carry trades, value options, and build macro dashboards using LSEG financial data and analytics.
Monte-Neo strategy verifier
Verify trading-strategy backtests: look-ahead probes, trading costs, Deflated Sharpe, walk-forward.
How to run each
LSEG As a Claude Code plugin
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install lseg@knowledge-work-pluginsMonte-Neo strategy verifier As a local MCP server: PyPI package
claude mcp add --transport stdio monte-neo -- uvx monte-neo mcpCommands 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: Monte-Neo strategy verifier · 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. 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.