Manifold vs TradingAgentStack
Manifold is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-09. 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 |  Manifold |  TradingAgentStack |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published 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
| Fact | Manifold | TradingAgentStack |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-09 |
| Where it runs (differs) | Remote server (api.manifold.markets/v0/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/intoapex/ai-trading-tools |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (6 h ago) | Status 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
Manifold
Tools for accessing the Manifold Markets online prediction market platform.
TradingAgentStack
Verified results for AI trading bots, vaults and algo strategies, plus safety scores and incidents.
How to run each
Manifold As a remote MCP server
claude mcp add --transport http manifold https://api.manifold.markets/v0/mcpTradingAgentStack As a remote MCP server
claude mcp add --transport http tradingagentstack https://tradingagentstack.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of TradingAgentStack responded at the last daily check. How we check endpoints
Tools each declares
Only Manifold has
get-betsget-marketget-usersearch-marketssearch-users
Only TradingAgentStack has
broker_order_gatingcheckcheck_setupcompare_toolsget_incidentsget_leaderboardget_riskget_toollist_categorysearch_tools
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (TradingAgentStack as of 2026-11-06). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Manifold · What it can do: TradingAgentStack · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.