mcp-registry/io.github.cachecarti/dmoera-creator · v1.30.0
Also listed as glama/cachecarti/dmoera-mcp-server
As of 2026-10-18 09:07 UTC, the Cachecarti Dmoera Creator MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Build, backtest, and deploy crypto trading strategies via MCP with 7-stage validation.
Claude Code
claude mcp add --transport http cachecarti-dmoera-creator-mcp-server https://dmoera.xyz/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"cachecarti-dmoera-creator-mcp-server": {
"type": "http",
"url": "https://dmoera.xyz/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
44 of 44 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
44 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
63 parameter(s) across 29 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
7 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,130 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 1 tool(s) removed and 11 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 29 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator/fixes
{
"name": "add_bot_to_fund",
"description": "Add a bot to a fund's roster.\n\n Personal funds can only contain the authenticated user's OWN bots.\n Use list_my_bots to see eligible strategies.\n\n Args:\n fund_id: The fund's ID.\n bot_id: The bot to add (e.g. \"momentum_eth_v3\").\n bot_domain: The bot's domain (e.g. \"eth_usdc\", \"btc_usdc\").\n weight: Initial allocation weight in percent (default 20.0).\n\n Returns the updated roster entry.\n ",
"inputSchema": {
"type": "object",
"title": "add_bot_to_fundArguments",
"required": [
"fund_id",
"bot_id",
"bot_domain"
],
"properties": {
"bot_id": {
"type": "string",
"title": "Bot Id"
},
"weight": {
"type": "number",
"title": "Weight",
"default": 20
},
"fund_id": {
"type": "integer",
"title": "Fund Id"
},
"bot_domain": {
"type": "string",
"title": "Bot Domain"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "close_fund",
"description": "Permanently close a hedge fund. Returns all capital to the wallet.\n\n This is irreversible. The fund's performance record is preserved for\n reporting and copy-trader settlement.\n\n Args:\n fund_id: The fund's ID.\n\n Returns success or error.\n ",
"inputSchema": {
"type": "object",
"title": "close_fundArguments",
"required": [
"fund_id"
],
"properties": {
"fund_id": {
"type": "integer",
"title": "Fund Id"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "create_fund",
"description": "Create a new personal hedge fund for the authenticated user.\n\n The fund starts inactive — call activate_fund to start Manager Mode.\n Initial capital is taken from the user's wallet_cash at creation time.\n Personal funds can ONLY contain the user's own bots — use list_my_bots\n to see eligible strategies.\n\n Args:\n fund_name: Display name for the fund.\n router_preset: Risk profile — one of \"prudent\", \"standard\",\n \"opportunistic\", \"unrestricted\".\n ",
"inputSchema": {
"type": "object",
"title": "create_fundArguments",
"properties": {
"fund_name": {
"type": "string",
"title": "Fund Name",
"default": "My Hedge Fund"
},
"philosophy": {
"type": "string",
"title": "Philosophy",
"default": ""
},
"router_preset": {
"type": "string",
"title": "Router Preset",
"default": "standard"
},
"aggression_mode": {
"type": "string",
"title": "Aggression Mode",
"default": "normal"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.cachecarti/dmoera-creator"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.cachecarti/dmoera-creator"}) over MCP.
swap_bot_in_fund ~295 tokensupdate_fund_caps ~262 tokenscreate_fund ~261 tokenssubmit_strategy ~255 tokenssandbox_backtest ~249 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.cachecarti%2Fdmoera-creator?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:47a8a131dcdd4d1b…, first seen 2026-10-17, included at leaf 4356 of 21,177. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable other servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 09:07 UTC, the Cachecarti Dmoera Creator MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Cachecarti Dmoera Creator MCP server advertises 44 tools, including activate_fund, add_bot_to_fund, close_fund, create_fund, deactivate_fund.
Point your MCP client at this streamable-http endpoint: https://dmoera.xyz/mcp
Glimind scanned all 44 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.