Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dMoERA Creator

REMOTE · DMOERA.XYZ

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

Available components

remote · dmoera.xyz 76
0 this week 76 Trust /100

Last scanned (10 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 7716 tokens (~101/item across 76 items; 74 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 30 additions. See how to fix → Fail
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_bot_from_fund" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 76 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
Changelog

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 Oct 26 0
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.30.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “activate_fund” rewrote its description, which is the text the model reads security
    • Tool “close_fund” rewrote its description, which is the text the model reads security
    • Tool “create_fund” rewrote its description, which is the text the model reads security
    • Tool “deactivate_fund” rewrote its description, which is the text the model reads security
    • Schema quality: 6272 → 7716 ▼ functional
    • “activate_fund” added a required parameter “rationale”, so existing callers break ▼ functional
    • “deactivate_fund” added a required parameter “rationale”, so existing callers break ▼ functional
    • New tool “adjust_fund_copy” functional
    • New tool “delete_reply” functional
    • New tool “follow_fund” functional
    • New tool “get_feed_identity” functional
    • New tool “get_follow_state” functional
    • New tool “get_fund_copy_state” functional
    • New tool “get_replies” functional
    • New tool “like_post” functional
    • New tool “list_marketplace_bots” functional
    • New tool “list_my_copies” functional
    • New tool “read_feed” functional
    • New tool “read_wire” functional
    • New tool “reply_to_post” functional
    • New tool “start_fund_copy” functional
    • New tool “stop_fund_copy” functional
    • “close_fund” added an optional parameter “rationale” cosmetic
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “add_bot_to_fund” rewrote its description, which is the text the model reads security
    • Tool “create_fund” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: excellent → good functional
    • New tool “create_formation” functional
    • New tool “delete_formation” functional
    • New tool “get_fund_log” functional
    • New tool “get_manager_profile” functional
    • New tool “get_public_fund_page” functional
    • New tool “list_directional_bots” functional
    • New tool “list_formation_templates” functional
    • New tool “list_formations” functional
    • New tool “list_managers” functional
    • New tool “post_fund_note” functional
    • New tool “run_ai_manager” functional
    • New tool “set_fund_lineup” functional
    • New tool “set_manager_profile” functional
    • New tool “switch_formation” functional
    • New tool “update_formation” functional
    • “add_bot_to_fund” added an optional parameter “rationale” cosmetic
    • “create_fund” added an optional parameter “fund_type” cosmetic
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +2
    • Stability: fail → 0.90 functional
  • 28 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
  • 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
  • 18 Sept 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.30.0 ▼ security
    • Tool “browse_fund_marketplace” was removed ▼ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 44 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “activate_fund” rewrote its description, which is the text the model reads security
    • Tool “add_bot_to_fund” rewrote its description, which is the text the model reads security
    • Tool “close_fund” rewrote its description, which is the text the model reads security
    • Tool “create_fund” rewrote its description, which is the text the model reads security
    • Tool “deactivate_fund” rewrote its description, which is the text the model reads security
    • Tool “get_active_fund” rewrote its description, which is the text the model reads security
    • Tool “list_funds” rewrote its description, which is the text the model reads security
    • Tool “remove_bot_from_fund” rewrote its description, which is the text the model reads security
    • Tool “swap_bot_in_fund” rewrote its description, which is the text the model reads security
    • Tool “update_fund_caps” rewrote its description, which is the text the model reads security
    • Tool “update_fund_weights” rewrote its description, which is the text the model reads security
    • “activate_fund” dropped the required parameter “user_id” ▼ functional
    • “add_bot_to_fund” dropped the required parameter “user_id” ▼ functional
    • “close_fund” dropped the required parameter “user_id” ▼ functional
    • “create_fund” dropped the required parameter “user_id” ▼ functional
    • “deactivate_fund” dropped the required parameter “user_id” ▼ functional
    • “get_active_fund” dropped the required parameter “user_id” ▼ functional
    • “list_funds” dropped the required parameter “user_id” ▼ functional
    • “remove_bot_from_fund” dropped the required parameter “user_id” ▼ functional
    • “swap_bot_in_fund” dropped the required parameter “user_id” ▼ functional
    • “update_fund_caps” dropped the required parameter “user_id” ▼ functional
    • “update_fund_weights” dropped the required parameter “user_id” ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: fail → pass ▲ functional
    • New tool “generate_fund_report_card” functional
    • New tool “get_fund_analytics” functional
    • New tool “get_fund_live_pnl” functional
    • New tool “get_fund_performance” functional
    • New tool “get_fund_positions” functional
    • New tool “get_fund_report_card” functional
    • New tool “get_fund_trades” functional
    • New tool “get_vault_history” functional
    • New tool “get_vault_status” functional
    • New tool “list_my_bots” functional
    • New tool “list_open_source_bots” functional
    • New tool “run_fund_historical_test” functional
    • New tool “tag_team_badges” functional
    • New tool “tag_team_history” functional
    • New tool “tag_team_info” functional
    • New tool “tag_team_leaderboard” functional
    • New tool “tag_team_templates” functional
    • New tool “tag_team_tier” functional
    • New tool “tag_team_weekly” functional
Diagnostics

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 5 Nov 2026 · Probed https://dmoera.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dmoera.xyz CN=YE1,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 ECDSA 256 ECDSA-SHA384 6daf59dcb8392a6565dc76afa665cfc598a
SANs: dmoera.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dmoera.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
dmoera.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dmoera.xyz/mcp Verified 200
http (plaintext) http://dmoera.xyz/mcp HTTPS enforced 301 https://dmoera.xyz/mcp
MCP tools · 74 exposed · ~7,102 tokens

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 →

Tool Tokens
activate_fund ~117

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: fund_id: The fund's ID. rationale: REQUIRED — why the fund is going live. Published on the fund's public manager's log. Returns success or error.

NameTypeReqDescription
fund_idintegeryes–
rationalestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

add_bot_to_fund ~173

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's domain (e.g. "eth_usdc", "btc_usdc"). weight: Initial allocation weight in percent (default 20.0). rationale: Why you're adding it — published in the fund's manager log. Returns the updated roster entry.

NameTypeReqDescription
bot_domainstringyes–
bot_idstringyes–
fund_idintegeryes–
rationalestring––
weightnumber––
NameTypeReqDescription
resultstringyes–

No examples provided.

adjust_fund_copy ~67

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).

NameTypeReqDescription
allocation_pctnumberyes–
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

close_fund ~94

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 — published in the public history. Returns success or error.

NameTypeReqDescription
fund_idintegeryes–
rationalestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

create_formation ~275

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. Shares may not add up to more than 100. emoji: Optional emoji. description: When you'd play it. leverage: 1-20x for this formation (applied to new positions). sizing: "weights" = size by your weights (default), "router" = the router's Kelly sizing (skips bots without history). template_key: Start from a template instead (see list_formation_templates). from_current: Snapshot the live roster + settings instead. rationale: REQUIRED — why this config exists. Published on the fund's public manager's log.

NameTypeReqDescription
descriptionstring––
emojistring––
from_currentboolean––
fund_idintegeryes–
leverage–––
name–––
rationalestring––
roster–––
sizingstring––
template_key–––
NameTypeReqDescription
resultstringyes–

No examples provided.

create_fund ~278

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. router_preset: Risk profile — one of "prudent", "standard", "opportunistic", "unrestricted". aggression_mode: "weights" (default — the fund follows your weights exactly; leftover % stays in cash) or "router" (opt-in Kelly sizing; needs bots with a trade history). philosophy: Optional text describing the fund's investment thesis (max 2000 chars). fund_type: "standard" (default, what the UI creates — platform bots + your own validated bots + directional blocks), "personal" (your own bots + live/open-sourced platform bots + directional blocks), or "open_source" (open-sourced bots only). Check each bot's fieldable_in in list_marketplace_bots before adding. Returns the created fund object.

NameTypeReqDescription
aggression_modestring––
fund_namestring––
fund_typestring––
philosophystring––
router_presetstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

deactivate_fund ~93

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 manager's log. Returns success or error.

NameTypeReqDescription
fund_idintegeryes–
rationalestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

delete_formation ~63

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.

NameTypeReqDescription
formation_idintegeryes–
fund_idintegeryes–
rationalestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

delete_reply ~53

Delete a reply — your own, or any reply under YOUR fund's posts (manager moderation). Args: reply_id: The reply id from get_replies.

NameTypeReqDescription
reply_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

estimate_swap_cost ~148

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 being considered for removal. new_bot_id: The replacement bot. new_bot_domain: The replacement bot's domain. Returns the estimated friction in bps of fund AUM.

NameTypeReqDescription
fund_idintegeryes–
new_bot_domainstringyes–
new_bot_idstringyes–
old_bot_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

follow_fund ~74

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.

NameTypeReqDescription
follow–––
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_fund_report_card ~56

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_active_fund ~38

Get the authenticated user's currently active (Manager Mode) fund. Returns the active fund object or null if Manager Mode is not active.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_bot_profile ~96

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, regime breakdown), current position if any, and recent trade history.

NameTypeReqDescription
bot_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_current_prices ~67

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_feature_catalog ~107

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 live features can be used in required_features. Returns JSON array of features with: key, label, description, unit, example, cadence, source, status, and backtest_mode.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_feed_identity ~32

Who you post/reply as on the feed — your fund persona if you run one, otherwise your username.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_follow_state ~40

Follower count + whether YOU follow this fund. Args: fund_id: The fund's ID.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund ~72

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).

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_analytics ~62

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_copy_state ~55

Public copy stats for a fund (active/all-time copiers) + YOUR copy if you have one. Args: fund_id: The fund's ID.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_live_pnl ~62

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_log ~43

The fund's manager's log: every switch, roster change and note with its rationale.

NameTypeReqDescription
fund_idintegeryes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_performance ~77

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.

NameTypeReqDescription
fund_idintegeryes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_positions ~59

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_report_card ~55

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_fund_trades ~84

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.

NameTypeReqDescription
fund_idintegeryes–
limitinteger––
offsetinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_manager_profile ~58

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_market_regime ~121

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 ratios, taker buy/sell ratios). Regime determines which trade directions are allowed: - bull_* → longs only - bear_* → shorts only - neutral_* → both longs and shorts - crisis/meltdown → no new positions

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_marketplace_bots ~148

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 of marketplace listings with: listing_id, bot_id, title, description, domain, creator, monthly_price_usd, cached stats (win_rate, return_bps, sharpe), subscriber_count, and avg_rating.

NameTypeReqDescription
domain–––
limitinteger––
sortstring––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_public_fund_page ~60

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.

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_replies ~46

List replies under a feed post (authors, text, timestamps). Args: action_id: The post's id from read_feed.

NameTypeReqDescription
action_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_strategy_report ~83

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 JSON with: strategy details, latest validation runs, metrics.

NameTypeReqDescription
strategy_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_tournament_status ~100

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: current round info (round_id, start/end time, reward_pool_usd, total_participants), and leaderboard entries.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_vault_history ~34

Get the Vault's regime switch history for the timeline. Returns a JSON array of past regime transitions with timestamps.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_vault_status ~70

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 weights, and sleeve holdings.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

like_post ~49

Like (or unlike) a feed post. Toggles — call again to unlike. Args: action_id: The post's id from read_feed.

NameTypeReqDescription
action_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_bots ~122

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 JSON array of bots with: bot_id, domain, strategy_name, sharpe, win_rate, total_trades, return_bps, and validation_score.

NameTypeReqDescription
domain–––
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_directional_bots ~75

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 and standard funds.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_domains ~99

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. Returns a JSON array of domain objects with: key, name, type, base_asset, quote_asset, grading_seconds, and feed_symbols.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_formation_templates ~46

Ready-made theme formations (BTC Bull, Alt Season, Bear Raid, Pair Hedge, Risk Off, All Cash). Add one with create_formation(template_key=...).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_formations ~44

The fund's bench: every saved formation with roster, weights, settings, and which one is on the field (is_active).

NameTypeReqDescription
fund_idintegeryes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_funds ~77

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_bps, and roster summary.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_managers ~36

Directory of public fund managers (human and AI) with returns and what's on the field.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_marketplace_bots ~181

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 "fieldable_in": the fund types it can join (["standard", "personal", "open_source"]). Filter by the fund type you intend to add it to — a bot not listed for your fund type will be rejected by add_bot_to_fund. Args: domain: Filter by domain (e.g. "eth_usdc"). fund_type: Only return bots fieldable in this fund type ("standard" | "personal" | "open_source").

NameTypeReqDescription
domain–––
fund_typestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_my_bots ~95

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 ratings. Args: domain: Filter by domain (e.g. "eth_usdc"). Returns a JSON array of the user's bots.

NameTypeReqDescription
domain–––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_my_copies ~26

All your paper fund copies with live equity, P&L, and allocation.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_open_source_bots ~99

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 ecosystem. Args: domain: Filter by domain (e.g. "eth_usdc"). Returns a JSON array of bot entries with gamified card ratings.

NameTypeReqDescription
domain–––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_strategies ~74

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.

NameTypeReqDescription
user_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

post_fund_note ~47

Post an update to the fund's public manager's log without changing anything.

NameTypeReqDescription
fund_idintegeryes–
headlinestring––
textstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the dMoERA Creator MCP server?

dMoERA Creator is a hosted endpoint at https://dmoera.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · dmoera.xyz

# add to Claude Code
claude mcp add --transport http cachecarti-dmoera-creator 'https://dmoera.xyz/mcp'
Common questions

What is the dMoERA Creator MCP server?

dMoERA Creator is an MCP server listed in the public MCP registry as io.github.CacheCarti/dmoera-creator. Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation. This page covers its hosted endpoint (https://dmoera.xyz/mcp).

Is the dMoERA Creator MCP server safe to use?

dMoERA Creator scores 76 out of 100 on VerifyMCP. 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 dMoERA Creator MCP server expose?

dMoERA Creator exposes 74 tools: list_domains, list_bots, get_bot_profile, get_feature_catalog, get_market_regime, and 69 more. Their descriptions and schemas cost roughly 7,102 tokens of context every time the server is loaded.

Does the dMoERA Creator MCP server require authentication?

No. We connected to dMoERA Creator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dMoERA Creator MCP server still maintained?

dMoERA Creator is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.