EventTrader MCP
PYPI · CYMETICA-EVENTTRADER-MCP · 2 COMPONENTS · SCANNED SEP 26
AI prediction market trading — real-time data, CLOB exchange, Prop Desk, 40+ tools
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5004 tokens (~86/item across 58 items; 58 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the EventTrader MCP server?
EventTrader MCP runs locally as a PyPI package, launched with uvx cymetica-eventtrader-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cymetica-eventtrader-mcp
claude mcp add com-cymetica-event-trader-mcp -- uvx cymetica-eventtrader-mcp
{
"mcpServers": {
"com-cymetica-event-trader-mcp": {
"command": "uvx",
"args": [
"cymetica-eventtrader-mcp"
]
}
}
} {
"servers": {
"com-cymetica-event-trader-mcp": {
"command": "uvx",
"args": [
"cymetica-eventtrader-mcp"
]
}
}
} codex mcp add com-cymetica-event-trader-mcp -- uvx cymetica-eventtrader-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-cymetica-event-trader-mcp": {
"type": "local",
"command": [
"uvx",
"cymetica-eventtrader-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-cymetica-event-trader-mcp --command uvx --arg cymetica-eventtrader-mcp
mcp_servers:
com-cymetica-event-trader-mcp:
command: "uvx"
args: ["cymetica-eventtrader-mcp"] {
"McpServers": {
"com-cymetica-event-trader-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"cymetica-eventtrader-mcp"
]
}
}
} assistant mcp add com-cymetica-event-trader-mcp -t stdio -c uvx -a cymetica-eventtrader-mcp
{
"mcpServers": {
"com-cymetica-event-trader-mcp": {
"command": "uvx",
"args": [
"cymetica-eventtrader-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +3
- License: fail → pass ▲ functional
- Licence: MIT License → MIT functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.1.4 → 1.1.5 functional
- 22 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed pypi/cymetica-eventtrader-mcp@1.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
et_register_bot ~235
Register a new trading bot and receive API credentials. Creates a new bot registration in Event Trader, generating unique API credentials for programmatic access. The bot will be assigned rate limits based on its tier. Args: params (RegisterBotInput): Validated input containing: - name (str): Bot name (3-50 chars) - bot_type (BotType): trading_bot, market_maker, arbitrage, sniper, or analytics - owner_wallet (str): Owner's wallet address - tier (BotTier): standard, premium, enterprise, or partner - description (Optional[str]): Bot description Returns: str: Response containing bot_id, api_key (store securely!), tier, status Rate Limits by Tier: - STANDARD: 100 req/min, 50k req/day - PREMIUM: 1k req/min, 500k req/day - ENTERPRISE: 10k req/min, 5M req/day - PARTNER: 100k req/min, 50M req/day
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_rotate_bot_key ~89
Rotate a bot's API credentials. Generates a new API key and invalidates the old one. Store the new key securely as it will only be shown once. Args: params (BotIdInput): Validated input containing: - bot_id (str): Bot ID to rotate key for Returns: str: New API key (store securely!)
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_simulate_trade ~132
Simulate rewards for a hypothetical trade. Calculate expected points, fees, and potential earnings before trading. Args: params (SimulateTradeInput): Validated input containing: - wallet (str): Wallet address (for tier info) - trade_amount (float): Trade amount in USD - market_id (Optional[str]): Market ID - side (str): 'yes' or 'no' - win_probability (float): Estimated win probability (0-1) Returns: str: Simulated rewards breakdown including points, fees, and potential profit
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_start_speed_round ~92
Start a 60-second betting frenzy round. Place as many bets as you can within the time limit for boost multipliers! Args: params (StartSpeedRoundInput): Validated input containing: - wallet (str): Wallet address - duration_seconds (int): Duration (30-120, default 60) Returns: str: Round ID and start time
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_submit_duel_prediction ~82
Submit a prediction for the current duel round. Args: params (SubmitDuelPredictionInput): Validated input containing: - duel_id (str): Duel ID - prediction (str): 'yes' or 'no' Returns: str: Round result, score update, and next question (if any)
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_submit_lever_prediction ~79
Submit a prediction for the current lever streak round. Args: params (SubmitLeverPredictionInput): Validated input containing: - game_id (str): Game ID - prediction (str): 'yes' or 'no' Returns: str: Round result, leverage update, and next question
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_update_bot ~103
Update a bot's configuration. Update bot name, description, or status. Cannot change bot type or tier. Args: params (UpdateBotInput): Validated input containing: - bot_id (str): Bot ID to update - name (Optional[str]): New name - description (Optional[str]): New description - status (Optional[BotStatus]): New status Returns: str: Updated bot configuration
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
et_use_boost ~81
Apply a boost to a trade. Args: params (UseBoostInput): Validated input containing: - wallet (str): Wallet address - boost_id (str): Boost ID to use - trade_id (str): Trade ID to apply boost to Returns: str: Confirmation with applied multiplier
| Name | Type | Req | Description |
|---|---|---|---|
| params | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the EventTrader MCP server?
EventTrader MCP is listed in the public MCP registry as com.cymetica/event-trader-mcp. AI prediction market trading, real-time data, CLOB exchange, Prop Desk, 40+ tools. This page covers its PyPI package (cymetica-eventtrader-mcp).
Is the EventTrader MCP server safe to use?
EventTrader MCP scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EventTrader MCP server expose?
EventTrader MCP exposes 58 tools: et_register_bot, et_get_bot, et_update_bot, et_delete_bot, et_rotate_bot_key, and 53 more. Their descriptions and schemas cost roughly 5,004 tokens of context every time the server is loaded.
Is the EventTrader MCP server still maintained?
EventTrader MCP is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the EventTrader MCP server under?
EventTrader MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.