Ext Ops Panel
Open dashboard
Comparison

Robinhood vs TradingAgentStack

Robinhood is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). TradingAgentStack is an MCP server published by intoApex. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
MarketplaceRobinhoodTradingAgentStack
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 661
Stars (GitHub): 15 895
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.0
Downloads/month (npm): 1 560
Downloads/week (npm): 111
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.7.0
Downloads/month (npm): 1 560
Downloads/week (npm): 111
Forks (GitHub): 0
Stars (GitHub): 0
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

Robinhood vs TradingAgentStack
FactRobinhoodTradingAgentStack
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)15 895 (better)0 (worse)
Forks (GitHub) (differs)1 661 (better)0 (worse)
Last release (differs)Not published2026-11-09
Where it runs (differs)Remote server (agent.robinhood.com/mcp/trading)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/cursor/pluginsgithub.com/intoapex/ai-trading-tools
Changes in the last 7 days (differs)06
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)Status out of date: last check 41 h ago returned HTTP 405Status out of date: last check 37 h ago returned HTTP 405

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

Robinhood

In its own words, on Cursor: cursor/plugins:

View portfolios, positions, orders, watchlists, and market data, and trade in a Robinhood Agentic account.

TradingAgentStack

In its own words, on Official MCP Registry:

Verified results for AI trading bots, vaults and algo strategies, plus safety scores and incidents.

How to run each

Robinhood

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

TradingAgentStack As a remote MCP server

Claude Code
claude mcp add --transport http tradingagentstack https://tradingagentstack.com/api/mcp

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of Robinhood nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Robinhood · What it can do: TradingAgentStack · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-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