io.github.KyuRish/trading212-mcp-server vs HoodL2 Projects
io.github.KyuRish/trading212-mcp-server is an MCP server published by KyuRish. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). HoodL2 Projects is an MCP server published by zeit-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  io.github.KyuRish/trading212-mcp-server |  HoodL2 Projects |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (PyPI): 491 Downloads/week (PyPI): 156 Forks (GitHub): 4 Stars (GitHub): 10 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.4.0 Downloads/month (PyPI): 491 Downloads/week (PyPI): 156 Forks (GitHub): 4 Stars (GitHub): 10 Not marked · First seen |
Not listed |
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 | io.github.KyuRish/trading212-mcp-server | HoodL2 Projects |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 10 | No figure on GitHub |
| Forks (GitHub) (differs) | 4 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (trading212-mcp-server) | Remote server (hoodl2.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kyurish/trading212-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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
io.github.KyuRish/trading212-mcp-server
MCP server for Trading 212 API - portfolio, orders, pies, dividends, and analytics
HoodL2 Projects
Search Robinhood Chain ecosystem projects, retrieve project details, and list categories.
How to run each
io.github.KyuRish/trading212-mcp-server As a local MCP server: PyPI package
claude mcp add --env "TRADING212_API_KEY=<YOUR_TRADING212_API_KEY>" --env "TRADING212_API_SECRET=<YOUR_TRADING212_API_SECRET>" --transport stdio trading212-mcp-server -- uvx trading212-mcp-serverRequires: TRADING212_API_KEY (secret), TRADING212_API_SECRET (secret)
HoodL2 Projects As a remote MCP server
claude mcp add --transport http hoodl2-projects https://hoodl2.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HoodL2 Projects 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
The marketplaces of HoodL2 Projects publish no settings it asks for, so we do not compare settings.
What it can do: io.github.KyuRish/trading212-mcp-server · What it can do: HoodL2 Projects · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.