dMoERA Creator
REMOTE · DMOERA.XYZ
Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation.
Available components
Last scanned (14 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 74 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 74 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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
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. | DS published | 3599, 18130 | 8, 8 | Verified |
| dmoera.xyz. | No DS | 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 |
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 →
read_feed ~207
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_config...), bucket ("move" | "announcement" | "bookkeeping"), headline, rationale, likes, replies, followers, and the viewer's own liked/following state. Args: limit: Posts to return (1-100, default 20). before: Cursor — pass the last post's id to page older posts. fund_id: Restrict to one fund's posts. tab: "all" (everything public) or "following" (funds you follow + your own).
| Name | Type | Req | Description |
|---|---|---|---|
| before | – | – | – |
| fund_id | – | – | – |
| limit | integer | – | – |
| tab | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_wire ~87
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: limit: Max wire posts to return (default 10).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_bot_from_fund ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_id | string | yes | – |
| fund_id | integer | yes | – |
| reason | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reply_to_post ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | integer | yes | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_ai_manager ~48
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).
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_fund_historical_test ~137
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 30 seconds per user. Args: roster: List of {"bot_id": str, "weight_pct": float} entries. initial_capital: Starting capital for the simulation (default 10000). Returns the simulated PnL time-series and diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| initial_capital | number | – | – |
| roster | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sandbox_backtest ~248
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 created. Use this for rapid iteration. Args: code: Python source code implementing the Strategy contract. Must define a METADATA dict and a class extending Strategy with an on_bar(ctx) -> Signal method. See CREATOR_API.md. domain: Trading domain (e.g. "eth_usdc", "btc_usdc", "sol_usdc"). symbol: Price symbol for historical data (e.g. "ETHUSDT"). user_id: Identifier for trial tracking (used for DSR correction). Returns JSON with: success, metrics (sharpe, sortino, win_rate, total_trades, return_bps, max_drawdown, regime_breakdown, exit_reason_breakdown), or error details if validation failed.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| domain | string | – | – |
| symbol | string | – | – |
| user_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_fund_lineup ~144
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, removed bots are closed at market, new bots open on their next signal (Always Long/Short bots open right away). The change and your rationale go into the fund's public history.
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| rationale | string | – | – |
| roster | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_manager_profile ~268
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", the platform's AI loop can run the fund on a schedule using ai_prompt. philosophy: The fund's investment philosophy (public). ai_prompt: System prompt for the platform AI manager (public). ai_enabled: Let the platform AI decide on a schedule. ai_cadence_hours: How often the AI decides (1-168). ai_use_search: Let the AI read live news via grounded search. socials: {"twitter": "@x", "website": "...", "discord", "telegram", "github", "youtube"}.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_cadence_hours | – | – | – |
| ai_enabled | – | – | – |
| ai_prompt | – | – | – |
| ai_use_search | – | – | – |
| avatar | – | – | – |
| fund_id | integer | yes | – |
| manager_kind | – | – | – |
| persona_name | – | – | – |
| philosophy | – | – | – |
| socials | – | – | – |
| tagline | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
start_fund_copy ~160
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 ones close, ~60s sync). PAPER ONLY — never touches a live account or an exchange. Live accounts are refused; running your own fund is also a conflict. Args: fund_id: The fund to copy. allocation_pct: % of your paper portfolio (1-100, default 100=all-in, which pauses your own router deployment by draining free cash).
| Name | Type | Req | Description |
|---|---|---|---|
| allocation_pct | number | – | – |
| fund_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
stop_fund_copy ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_strategy ~289
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 data (70/30 split) 4. walk_forward — rolling window validation 5. randomized_start — different random start points 6. perturbation — market stress test 7. holdout — server-side reserved data (pass/fail only) If all stages pass, the strategy is registered for isolated live paper trading with status="incubating". Promotion to "live" requires a proven track record. Args: name: Human-readable strategy name (e.g. "ETH Momentum v2"). domain: Trading domain key (e.g. "eth_usdc"). code: Python source code implementing the Strategy contract. user_id: The creator's user ID. symbol: Price symbol for historical data. Returns JSON with: success, strategy_id, bot_id, validation results per stage, or error details.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| domain | string | yes | – |
| name | string | yes | – |
| symbol | string | – | – |
| user_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
swap_bot_in_fund ~188
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: The bot to add in its place. new_bot_domain: The new bot's domain (e.g. "eth_usdc"). weight: Allocation weight for the new bot (defaults to old bot's weight). reason: Optional reason for the swap. Returns the updated roster entry and friction estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| new_bot_domain | string | yes | – |
| new_bot_id | string | yes | – |
| old_bot_id | string | yes | – |
| reason | string | – | – |
| weight | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
switch_formation ~136
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 normal fund rules; any rejected are listed in the result. The rationale is published on the fund's public manager's log — write it for the fund's followers.
| Name | Type | Req | Description |
|---|---|---|---|
| formation_id | integer | yes | – |
| fund_id | integer | yes | – |
| mode | string | – | – |
| rationale | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_badges ~53
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_history ~20
Get the authenticated user's past Tag Team sessions with scores.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_info ~99
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 combined PnL is scored on the daily leaderboard. Returns session state, open positions, bot status, and rank.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_leaderboard ~75
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).
| Name | Type | Req | Description |
|---|---|---|---|
| date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_templates ~63
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_tier ~72
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).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
tag_team_weekly ~23
Get weekly championship standings (best 5 daily scores per user).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_formation ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| emoji | – | – | – |
| formation_id | integer | yes | – |
| fund_id | integer | yes | – |
| leverage | – | – | – |
| name | – | – | – |
| rationale | string | – | – |
| roster | – | – | – |
| sizing | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_fund_caps ~142
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 detector can veto trades. Only provided fields are updated; others remain unchanged. Returns success or error.
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| max_per_bot_pct | – | – | – |
| max_per_domain_pct | – | – | – |
| regime_veto_enabled | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_fund_weights ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fund_id | integer | yes | – |
| weights | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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
claude mcp add --transport http cachecarti-dmoera-creator 'https://dmoera.xyz/mcp'
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.
What did VerifyMCP test on the dMoERA Creator MCP server?
VerifyMCP ran 12 checks on dMoERA Creator, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about dMoERA Creator: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.