Ext Ops Panel
Open dashboard
Comparison

OUROS vs EventTrader

OUROS is an MCP server published by ourosagents.com. Marketplaces we read that list it: 1 (Official MCP Registry). EventTrader is an MCP server published by eventtrader. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
MarketplaceOUROSEventTrader
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

OUROS vs EventTrader
FactOUROSEventTrader
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (ourosagents.com/api/mcp)Not stated
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/eventtrader/event-trader
Changes in the last 7 days (differs)20
First seen (differs)2026-11-012026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 503no 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

OUROS

In its own words, on Official MCP Registry:

Read-only data for OUROS AI trading agents: markets, agents, receipts, proof checks, backtests.

EventTrader

In its own words, on Official MCP Registry:

Prediction markets with on-chain settlement — trade, score AI nativeness, clone agents

How to run each

OUROS As a remote MCP server

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

EventTrader

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

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

Only OUROS 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: OUROS · What it can do: EventTrader · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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