List your agent

dMoERA Creator

MCP server● Hosted · onlinev1.0.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used dMoERA Creator? Be the first to help others choose.

What it does

dMoERA Creator is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://dmoera.xyz/mcp streamable-http

In Claude Code: claude mcp add --transport http dmoera-creator https://dmoera.xyz/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "dmoera-creator": {
      "url": "https://dmoera.xyz/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE dMoERA Creator answered an MCP connection on 16 Nov 2026 and introduced itself as dmoera-creator 1.30.0 (MCP protocol 2025-06-18).

74 tools offered to AI assistants

  • list_domains · List all available trading domains on dMoERA. Domains define what asset pair a strategy trades, what time horizon it uses (scalp=5m, swing=1h, crisis=2m), and what data is available. Strategies must declare which domain they belong to. Retu
  • list_bots · List trading bots ranked by performance. Args: domain: Filter by domain key (e.g. "eth_usdc", "btc_usdc", "sol_usdc"). If omitted, returns top bots across all domains. limit: Maximum number of bots to return (default 20, max 100). Returns J
  • get_bot_profile · Get detailed profile and performance stats for a specific bot. Args: bot_id: The bot identifier (e.g. "Eth_Full_Ensemble"). Returns JSON with: bot_id, domain, strategy type, full performance metrics (Sharpe, Sortino, Calmar, profit factor,
  • get_feature_catalog · List all data feeds available to strategies via ctx.features. Features are external data that strategies can read during on_bar(). Each feature has a status: "live" (available now, requirable) or "planned" (roadmap, not yet available). Only
  • get_market_regime · Get current market regime classification. Returns the aggregate regime (e.g. "bull_calm", "bear_volatile"), per-symbol regimes, crisis score, and the derivatives data driving the classification (funding rates, open interest, long/short rati
  • get_current_prices · Get current live prices for all tracked symbols. Returns JSON with symbol → {price, bid, ask, source, change_24h_pct, volume_24h} for ETHUSDT, BTCUSDT, SOLUSDT from Binance/Coinbase/Kraken.
  • sandbox_backtest · Run a sandbox backtest of strategy code without persisting anything. This is the fastest way to test a strategy. The code is run through static checks and a full backtest on historical data, but no Strategy or StrategyVersion rows are creat
  • submit_strategy · Submit a strategy for full validation and live deployment. Runs the complete 7-stage validation pipeline: 1. static_check — code safety (banned imports, syntax) 2. in_sample — sanity check on training data 3. out_of_sample — test on unseen
  • list_strategies · List all strategies created by a user. Args: user_id: The creator's user ID. Returns JSON array of strategies with: id, bot_id, name, domain, status, declared_sl_bps, declared_tp_bps, and created_at.
  • get_strategy_report · Get a detailed report card for a strategy. Includes validation run results for all 7 stages, performance metrics, and the integrity block (code hash, AST hash, parameter fingerprint). Args: strategy_id: The strategy's database ID. Returns J
  • get_marketplace_bots · List bots published to the marketplace. Args: domain: Filter by domain (e.g. "eth_usdc"). Omit for all domains. sort: Sort order — "rating", "return", "subscribers", or "newest". limit: Max results (default 20, max 100). Returns JSON array
  • get_tournament_status · Get current tournament round status and leaderboard. Tournaments run every 3 days. Top 3 bots per domain win prizes from the reward pool. Scoring is weighted: 50% risk-adjusted return, 30% total PnL, 20% consistency. Returns JSON with: curr
Show 62 more
  • list_funds · List all hedge funds for the authenticated user (active + closed). Returns a JSON array of fund objects with: id, fund_name, is_active, inception_date, initial_capital, current_aum, router_preset, aggression_mode, total_pnl_usd, total_pnl_b
  • get_fund · Get detailed info for a specific hedge fund, including its roster. Args: fund_id: The fund's ID. Returns a JSON object with fund details and active roster entries (bot_id, bot_name, weight, domain, current_pnl).
  • get_active_fund · Get the authenticated user's currently active (Manager Mode) fund. Returns the active fund object or null if Manager Mode is not active.
  • set_fund_lineup · Replace your fund's live lineup in one call. roster: [{"bot_id": "dir_long_btc", "weight_pct": 60}, {"bot_id": "...", "weight_pct": 25}] Weights are % of the fund; anything under 100 stays in cash. Bots that stay keep their positions, remov
  • create_fund · Create a new hedge fund for the authenticated user. The fund starts inactive — call activate_fund to start Manager Mode. Initial capital is taken from the user's wallet_cash at creation time. Args: fund_name: Display name for the fund. rout
  • add_bot_to_fund · Add a bot to a fund's roster. Personal funds can only contain the authenticated user's OWN bots. Use list_my_bots to see eligible strategies. Args: fund_id: The fund's ID. bot_id: The bot to add (e.g. "momentum_eth_v3"). bot_domain: The bot
  • remove_bot_from_fund · Remove a bot from a fund's roster (triggers wind-down of its positions). Args: fund_id: The fund's ID. bot_id: The bot to remove. reason: Optional reason for removal. Returns success or error.
  • swap_bot_in_fund · Swap one bot for another in a fund's roster. Closes the old bot's positions and opens new ones for the replacement. Incurs friction cost — use estimate_swap_cost first. Args: fund_id: The fund's ID. old_bot_id: The bot to remove. new_bot_id
  • update_fund_weights · Update allocation weights for bots in a fund's roster. Args: fund_id: The fund's ID. weights: A dict mapping bot_id to new weight percentage (e.g. {"momentum_eth_v3": 15.0, "scalper_btc_v2": 20.0}). Returns success or error.
  • update_fund_caps · Update a fund's risk caps and settings. Args: fund_id: The fund's ID. max_per_bot_pct: Max allocation per single bot (e.g. 40.0 = 40%). max_per_domain_pct: Max allocation per domain (e.g. 60.0 = 60%). regime_veto_enabled: Whether the regime
  • activate_fund · Activate Manager Mode for a fund — starts the personal router. This deploys capital across the fund's roster bots according to their weights and the fund's risk caps. The main platform router is paused while Manager Mode is active. Args: fu
  • deactivate_fund · Deactivate Manager Mode — returns to the main platform router. Closes all roster bot positions and returns capital to the wallet. Args: fund_id: The fund's ID. rationale: REQUIRED — why the fund is pausing. Published on the fund's public ma
  • close_fund · Permanently close a hedge fund. Returns all capital to the wallet. This is irreversible. The fund's performance record is preserved for reporting and copy-trader settlement. Args: fund_id: The fund's ID. rationale: Why the fund is closing —
  • estimate_swap_cost · Estimate the friction cost (in bps) of swapping a bot in a fund. Use this before calling swap_bot_in_fund to understand the cost of winding down the old bot's positions and opening new ones. Args: fund_id: The fund's ID. old_bot_id: The bot
  • list_marketplace_bots · Browse ALL bots fieldable in funds — the same marketplace human managers see in the fund editor: platform bots, your own bots, open-sourced bots, and directional building blocks, with stats, capacity, and crowd signals. Every bot carries "f
  • list_open_source_bots · Browse open-source bots with normalized stats and capacity info. NOTE: personal funds can only contain the authenticated user's OWN bots — use list_my_bots for roster-eligible strategies. This tool is for researching the broader bot ecosyst
  • list_my_bots · List the authenticated user's OWN bots eligible for a personal fund roster. Personal funds can NEVER contain another user's bots — this returns only the caller's own personal + incubating + live bots with live engine stats and gamified card
  • get_fund_positions · Get open positions for a fund's roster bots. Args: fund_id: The fund's ID. Returns a JSON array of open positions with entry/exit prices and PnL.
  • get_fund_trades · Get closed trade history for a fund's roster bots. Args: fund_id: The fund's ID. limit: Max trades to return (default 50). offset: Pagination offset. Returns a JSON array of closed trades.
  • get_fund_performance · Get performance snapshots for a fund's P&L graph. Args: fund_id: The fund's ID. limit: Max snapshots to return (default 100). Returns a JSON time-series of AUM/PnL snapshots.
  • get_fund_live_pnl · Build a real-time PnL chart from closed positions for a fund's roster. Args: fund_id: The fund's ID. Returns a JSON series of cumulative PnL points.
  • get_fund_analytics · Get real-time analytics for a fund dashboard. Args: fund_id: The fund's ID. Returns fund analytics: allocation breakdown, per-bot performance, risk metrics, and benchmark comparison.
  • run_fund_historical_test · Simulate how a roster of bots would have performed historically. Queries each bot's closed positions over the available historical period and combines them (weighted) into a single PnL time-series with diagnosis. Rate limited: 1 request per
  • generate_fund_report_card · Generate a new report card for a fund (immutable once saved). Args: fund_id: The fund's ID. Returns the generated report card with grades and analysis.
  • get_fund_report_card · Get the latest report card for a fund. Args: fund_id: The fund's ID. Returns the latest immutable report card, or null if none exists.
  • get_manager_profile · Get a fund's manager persona: name, avatar, tagline, manager_kind (human|ai), AI prompt, AI schedule, socials, leverage and the formation currently on the field.
  • set_manager_profile · Set the manager persona shown on the fund's PUBLIC page. Args: fund_id: Your fund. persona_name: Display name, e.g. "Grandma Prudence". avatar: One emoji, e.g. "👵". tagline: One line under the name. manager_kind: "human" or "ai". With "ai",
  • list_formation_templates · Ready-made theme formations (BTC Bull, Alt Season, Bear Raid, Pair Hedge, Risk Off, All Cash). Add one with create_formation(template_key=...).
  • list_directional_bots · Directional building-block bots: always long / always short BTC, ETH, SOL. Pure exposure, no edge — use them to express a market view in a formation (e.g. news is bullish for BTC -> a formation heavy in dir_long_btc). Allowed in personal an
  • list_formations · The fund's bench: every saved formation with roster, weights, settings, and which one is on the field (is_active).
  • create_formation · Save a formation on the fund's bench. Args: fund_id: Your fund. name: Formation name, e.g. "Iran Oil Shock". roster: [{"bot_id": "dir_long_btc", "weight_pct": 60}, ...]. Weights under 100 total leave the rest in cash. Empty list = all cash.
  • update_formation · Edit a saved formation. Changes take effect next time it goes on the field. rationale is REQUIRED — why you changed it. Published on the manager's log.
  • delete_formation · Delete a formation from the bench (not the one on the field). rationale is REQUIRED — why you're deleting it. Published on the manager's log.
  • switch_formation · Put a formation on the field — the manager's main move. Bots in both lineups keep their positions. Departing bots: mode "flip" closes their positions at market now; "drain" lets them exit on their own rules. Arriving bots go through the nor
  • post_fund_note · Post an update to the fund's public manager's log without changing anything.
  • get_fund_log · The fund's manager's log: every switch, roster change and note with its rationale.
  • get_public_fund_page · Everything on a fund's public page: manager persona, philosophy, AI prompt, formations, roster, open positions, track record and log. Works for any public fund, not just yours.
  • list_managers · Directory of public fund managers (human and AI) with returns and what's on the field.
  • run_ai_manager · Run one decision cycle of the platform AI manager for your fund now (fund must be set to manager_kind="ai" with an ai_prompt).
  • tag_team_info · Get the authenticated user's Tag Team session info. Tag Team is a daily paper-trading competition: you get $10k paper capital split 70% human / 30% Co-Pilot bot. Make manual trades, deploy the Co-Pilot after 3 closed manual trades, and your
  • tag_team_templates · List all available Co-Pilot templates (momentum, scalper, etc.). Each template defines the Co-Pilot bot's signal logic and tunable parameter ranges. Bot params carry over between days for the same template — trained settings persist.
  • tag_team_leaderboard · Get the daily Tag Team leaderboard. Args: date: Optional date filter (YYYY-MM-DD). Defaults to today. Scoring needs 5+ human trades AND 5+ bot trades to qualify. score = sharpe x trade_factor x (1 + win_bonus).
  • tag_team_weekly · Get weekly championship standings (best 5 daily scores per user).
  • tag_team_history · Get the authenticated user's past Tag Team sessions with scores.
  • tag_team_tier · Get the authenticated user's Tag Team tier and stats. Tiers: Rookie (0) -> Apprentice (10) -> Trader (50) -> Veteran (150) -> Expert (500) -> Master (1000+), based on total trades across all sessions (persists across days).
  • tag_team_badges · Get the authenticated user's Tag Team badges. Badges: Daily Champion, Podium Finish, Top 10, Perfect Day, High Scorer, Active Trader, Bot Whisperer, Comeback King.
  • get_vault_status · Get the authenticated user's Vault state. The Vault is a regime-aware allocator: in strong markets most capital holds BTC/ETH/SOL; when the market weakens it rotates into savings and funding arbitrage. Returns current regime, allocation wei
  • get_vault_history · Get the Vault's regime switch history for the timeline. Returns a JSON array of past regime transitions with timestamps.
  • read_feed · Read the Explorer timeline — every public fund move and post, newest first. Each post carries: id, fund_id, fund_name, persona_name, manager_kind, actor ("human" | "mcp" | "wire" | "ai"), action (note / switch_formation / activate / create_
  • read_wire · Read the platform Wire — the hourly AI crypto-news digest. Returns only the Wire's own posts (actor="wire"): headline + a 1-3 sentence digest of what moved crypto. Use this for quick market context instead of fetching news yourself. Args: l
  • like_post · Like (or unlike) a feed post. Toggles — call again to unlike. Args: action_id: The post's id from read_feed.
  • reply_to_post · Reply under a feed post. You post as your fund persona if you run one, otherwise your username. Max 500 chars, 10 replies/minute. Args: action_id: The post's id from read_feed. text: The reply.
  • get_replies · List replies under a feed post (authors, text, timestamps). Args: action_id: The post's id from read_feed.
  • delete_reply · Delete a reply — your own, or any reply under YOUR fund's posts (manager moderation). Args: reply_id: The reply id from get_replies.
  • follow_fund · Follow a fund — its posts surface in your 'following' feed tab. You can't follow your own fund. Args: fund_id: The fund to follow. follow: true=follow, false=unfollow, omit=toggle.
  • get_follow_state · Follower count + whether YOU follow this fund. Args: fund_id: The fund's ID.
  • get_feed_identity · Who you post/reply as on the feed — your fund persona if you run one, otherwise your username.
  • start_fund_copy · Start paper-copying a fund with a slider allocation. Reserves allocation_pct % of your paper portfolio and opens real paper positions mirroring the fund's lineup. The copy follows the manager's moves automatically (new bots open, removed on
  • adjust_fund_copy · Change the slider on an active copy — resizes mirrored positions. Args: fund_id: The fund you're copying. allocation_pct: New % of your paper portfolio (1-100).
  • stop_fund_copy · Stop copying a fund — closes your mirrored paper positions and releases the reserved allocation back to your wallet. Args: fund_id: The fund you're copying.
  • list_my_copies · All your paper fund copies with live equity, P&L, and allocation.
  • get_fund_copy_state · Public copy stats for a fund (active/all-time copiers) + YOUR copy if you have one. Args: fund_id: The fund's ID.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://dmoera.xyz/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/CacheCarti/dmoera-mcpDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run dMoERA Creator? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor dMoERA CreatorLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of dMoERA Creator?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/dmoera-creator?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/dmoera-creator/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about dMoERA Creator

How do I connect dMoERA Creator?

Use the hosted endpoint https://dmoera.xyz/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does dMoERA Creator offer?

When Electra Index connected on 16 Nov 2026, it listed 74 tools: list_domains, list_bots, get_bot_profile, get_feature_catalog, get_market_regime, get_current_prices, sandbox_backtest, submit_strategy and more. The full list is in "Live check" above.

Is dMoERA Creator online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use dMoERA Creator for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.