Back to Browse

Dmoera MCP Server

Developer ToolsUse Caution4.2MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation.

About

Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation.

Remote endpoints: streamable-http: https://dmoera.xyz/mcp

Security Report

4.2
Use Caution4.2High Risk

This is a well-structured MCP server that acts as a thin HTTP API client for the dMoERA trading platform. Authentication is properly handled through environment variables and HTTP headers with no hardcoded credentials. The code has good input validation and error handling. Minor concerns include broad exception handling and some informational logging issues, but these do not significantly impact security. Permissions (network_http, env_vars) appropriately match the server's purpose as a trading strategy discovery and backtesting tool. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 5 high severity).

3 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

dMoERA Creator Studio — MCP Server

smithery badge

Build, backtest, and deploy crypto trading strategies using any MCP-compatible AI agent (Claude, Cursor, Windsurf, Devin, Copilot, etc.).

What it does

The dMoERA MCP server exposes the dMoERA Creator API as Model Context Protocol tools. Your AI agent can:

  • Discover trading domains, data feeds, and market regimes
  • Inspect existing bots and their live performance metrics
  • Backtest strategy code in a sandboxed environment
  • Submit strategies for full 7-stage validation and live deployment
  • Monitor tournament status, leaderboard rankings, and strategy report cards

This is a thin API client — it talks to a running dMoERA backend via HTTP. No internal dMoERA code is required.

Installation

Prerequisites

  • Python 3.11+
  • The mcp Python package (pip install mcp)
  • A running dMoERA backend (or connect to the public instance)

Setup

git clone https://github.com/CacheCarti/dmoera-mcp.git
cd dmoera-mcp
pip install -r requirements.txt

MCP Configuration

Add this standard MCP configuration to Claude Desktop, Cursor, Windsurf, or another MCP client:

{
  "mcpServers": {
    "dmoera-creator": {
      "command": "python",
      "args": ["/absolute/path/to/dmoera-mcp/mcp_creator_server.py"],
      "env": {
        "DMOERA_API_URL": "https://dmoera.xyz",
        "DMOERA_API_KEY": "your_optional_personal_access_token"
      }
    }
  }
}

The API key is optional for public market data and discovery tools. Create a Personal Access Token at dmoera.xyz under Settings → API Keys to backtest, submit, fork, open-source, or delist strategies. Never commit your token.

Remote clients can connect through the Streamable HTTP endpoint:

https://dmoera.xyz/mcp

Tools

ToolDescriptionAuth Required
list_domainsList all available trading domains (ETH, BTC, SOL — spot and scalp)No
list_botsList trading bots ranked by performance, optionally filtered by domainNo
get_bot_profileGet detailed profile and performance stats for a specific botNo
get_feature_catalogList all data feeds available to strategies via ctx.featuresNo
get_market_regimeGet current market regime classificationNo
get_current_pricesGet current live prices for all tracked symbolsNo
sandbox_backtestBacktest strategy code in a sandboxed environmentYes
submit_strategySubmit a strategy for full validation and live deploymentYes
list_strategiesList all strategies created by a userYes
get_strategy_reportGet a detailed report card for a strategyNo
get_marketplace_botsList bots published to the marketplaceNo
get_tournament_statusGet current tournament round status and leaderboardNo
open_source_strategyPublish an eligible rejected strategy to the open-source leaderboardYes
fork_strategyRetrieve and fork an open-source strategyYes
get_open_source_leaderboardBrowse open-source strategies with FIFA-style ratingsNo
delist_strategyRetire or permanently delist one of your strategiesYes

Resources

  • creator-api://docs — Full strategy contract documentation
  • creator-api://strategy-template — Copy-pasteable strategy template

Example Usage

Ask your AI agent:

"List all trading domains on dMoERA, then backtest a simple RSI mean-reversion strategy for ETH/USDC."

The agent will call list_domains, inspect the available markets, then call sandbox_backtest with strategy code it generates. You can iterate:

"The Sharpe is too low. Try adding a volatility filter — only trade when ATR is above its 20-period average."

"Submit this strategy to the ETH/USDC domain."

The agent calls submit_strategy, which runs the full 7-stage validation pipeline. If it passes, the strategy enters the live Arena and competes for tournament payouts.

Strategy Contract

Strategies subclass Strategy and implement on_bar(self, ctx) -> Signal. See the creator-api://docs resource for the full contract.

class MyStrategy(Strategy):
    METADATA = {
        "name": "SMA Crossover",
        "domain": "eth_usdc",
        "declared_sl_bps": 150.0,
        "declared_tp_bps": 300.0,
        "declared_hold_seconds": 3600,
        "warmup_bars": 20,
        "required_features": [],
    }

    def on_bar(self, ctx):
        closes = ctx.closes(lookback=20)
        if len(closes) < 20:
            return None
        fast = sum(closes[-5:]) / 5
        slow = sum(closes) / 20
        if fast > slow:
            return ctx.signal(
                direction=SignalDirection.LONG,
                confidence=0.7,
                stop_loss_bps=150.0,
                take_profit_bps=300.0,
                horizon_seconds=3600,
            )
        return None

Tournament System

Bots compete in 3-day tournament rounds. Scoring is based on the bot's own performance:

  • 50% risk-adjusted (rolling Sharpe ratio)
  • 30% total return (log-scaled bps)
  • 20% consistency (win rate × trade volume)

Top 3 per domain win USDT from the reward pool. No user following needed to qualify — your bot competes on its own metrics.

Links

License

MIT

Reviews

No reviews yet

Be the first to review this server!