mcp-registry/io.github.austin-starks/nexustrade-mcp · v1.0.0
Also listed as glama/austin-starks/nexustrade-financial-mcp
As of 2026-10-24 00:34 UTC, the Austin Starks Nexustrade MCP server is up (it requires sign-in) with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 120.1 hours.
Quant research, backtesting, marketplace subscriptions, editable forks, copy trading, and execution.
Claude Code
claude mcp add --transport http austin-starks-nexustrade-mcp-server https://nexustrade.io/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"austin-starks-nexustrade-mcp-server": {
"type": "http",
"url": "https://nexustrade.io/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Loading this server's tool list costs an agent ~155,005 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
3 tool definition(s) exceed ~1,200 tokens each (largest: update_portfolio, ~57,880).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~146,456 tokens every session. How to fix →
24 of 24 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 →
8 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 →
6 parameter(s) across 2 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 →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
In the last 30 days: 0 tool(s) removed and 8 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. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.austin-starks%2Fnexustrade-mcp/fixes
{
"name": "approve_agent_plan",
"description": "⚠ INDIRECTLY COSTS LLM CREDITS — approving the plan unfreezes the agent which then runs more planning + execution LLM calls. Manual approval required; do NOT call unless the user explicitly told you to advance their Aurora agent. Approve a semi-automated agent that is waiting in pending_plan_approval or pending_action_approval. Auto-detects which approval the agent needs and emits the matching state-machine event so the agent resumes execution. Returns 400 if the agent is not in a pending-approv",
"inputSchema": {
"type": "object",
"required": [
"agentId"
],
"properties": {
"agentId": {
"type": "string",
"description": "MongoDB agent _id to approve"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "archive_agent",
"description": "Aurora agent surface (no LLM cost — pure DB write). Only relevant when managing Aurora agents. Archive an agent (soft-delete). The agent remains in the database but is hidden from default listings. Address by agentId OR exact title (XOR).",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"title": {
"type": "string",
"description": "Exact case-insensitive user-assigned title (XOR with agentId)"
},
"agentId": {
"type": "string",
"description": "MongoDB agent _id to archive (XOR with title)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "create_agent",
"description": "⚠ COSTS LLM CREDITS on the NexusTrade account — spins up an Aurora agent via Router V5 classification + ReAct execution loops, billed per token. **Manual approval required**: do NOT call unless the user explicitly asked to launch an Aurora agent. For strategy creation/backtesting/analysis prefer no-LLM tools: structured create_portfolio (pass full IPortfolio JSON), backtest_portfolio, query_backtest_history, query_*, fetch_portfolios. Create a new autonomous Aurora agent using the same body shap",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"title": {
"type": "string",
"description": "Optional user-assigned display name for the new agent (max 100 chars). Enables later lookup via title on get_agent / send_agent_message / etc."
},
"messages": {
"type": "array",
"items": {
"type": "object",
"required": [
"sender",
"content"
],
"properties": {
"data": {
"type": "object",
"description": "Optional message metadata"
},
"sender": {
"type": "string",
"description": "Message sender, usually User"
},
"content": {
"type": "string",
"description": "Message content"
},
"timestamp": {
"type": "string",
"description": "Optional ISO timestamp"
}
}
},
"description": "ChatMessage array, e.g. [{\"sender\":\"User\",\"content\":\"...\"}]"
},
"maxIterations": {
"type": "number",
"description": "Max agent iterations. When omitted, uses the user's saved ChatSettings.agentIterations (same as the web UI)."
},
"session_depth": {
"enum": [
"smart",
"deep"
],
"type": "string",
"description": "Deprecated compatibility field. Both values use Aurora's adaptive routing policy."
},
"attachment_ids": {
"type": "array",
"items": {
"type": "string"
},
"description": "READY chat-attachment ids from upload_chat_attachment. Bound onto the last user message as fileAttachments (same refs as the web FILES tab)."
},
"automationMode": {
"enum": [
"automated",
"semi-automated"
],
"type": "string",
"description": "automated | semi-automated. When omitted, uses ChatSettings.agentAutomationMode."
},
"conversationId": {
"type": "string",
"description": "Optional NexusGenAI conversation id"
},
"idempotencyKey": {
"type": "string",
"description": "Caller-chosen token that makes this create retry-safe. Creation runs the router and the planner and regularly takes longer than the transport will wait, so a call that times out has usually SUCCEEDED. Pass a unique key, and if the call appears to fail, retry with the SAME key: you get the agent the first call created, never a second billed run. A key reused for a different prompt is rejected rather than silently replayed."
}
}
},
"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.austin-starks/nexustrade-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.austin-starks/nexustrade-mcp"}) over MCP.
update_portfolio ~57,880 tokenscreate_portfolio ~45,191 tokensbuild_portfolio ~45,185 tokensbacktest_portfolio ~856 tokenscreate_agent ~696 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.austin-starks%2Fnexustrade-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.austin-starks%2Fnexustrade-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.austin-starks%2Fnexustrade-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.austin-starks%2Fnexustrade-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.austin-starks%2Fnexustrade-mcp?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:bfe321bbdf9d3131…, first seen 2026-10-17, included at leaf 14596 of 55,750. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable files servers · most reliable finance servers · most reliable data servers · most reliable knowledge 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-24 00:34 UTC, the Austin Starks Nexustrade MCP server is up (it requires sign-in) with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 120.1 hours.
Austin Starks Nexustrade MCP server advertises 27 tools, including approve_agent_plan, archive_agent, backtest_portfolio, build_portfolio, clone_strategies_to_portfolio.
Point your MCP client at this streamable-http endpoint: https://nexustrade.io/api/mcp
Glimind scanned all 24 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.