TL;DR
Connect the Muse personal agent through a NexusTrade Custom Connector, complete sign-in and request a dated public SEC filing. Muse Code uses separate setup. For owned portfolios, check the returned account and portfolio identity before making changes. A research brief, historical backtest, paper observation and brokerage deployment are separate tasks; connector authentication alone does not authorize them.
Connect Meta Muse in the intended environment
Create a Custom Connector named NexusTrade. Use the remote Streamable HTTP MCP endpoint https://nexustrade.io/api/mcp. Read the server authentication discovery and tool schemas. Guide me through NexusTrade sign-in and list the available tools. Do not place orders, activate portfolios, run backtests or change account settings.Scroll horizontally to read the full command, or copy it.
- Exact endpoint
- https://nexustrade.io/api/mcp; remote Streamable HTTP with account authentication.
Open Muse and send the Custom Connector request below. Review the proposed NexusTrade endpoint and tools, then finish NexusTrade sign-in using the private authentication flow. Muse Code has a separate setup; this path is for the Muse personal agent.
Try a public filing read in Meta Muse
Inspect the request
Run the public filing request after connecting. A fresh response may return a later filing; compare its reporting period, filing date and source URL.
Recorded NexusTrade filing reference
NexusTrade MCP sec_edgar returned this listing in Codex on 2026-10-12. Use it as a reference when checking your own connection.
Show the table · 5 rows, 2 columns
| Returned field | Recorded result |
|---|---|
| Company | Apple Inc. |
| Form | 10-Q |
| Filing date | 2026-07-31 |
| Period ended | 2026-06-27 |
| Accession | 0000320193-26-000020 |
No matching rows. Clear the filter to see all records.
Choose a separate next task
These guides are independent choices after the connection check. Review any proposed paid research, historical test or portfolio change before authorizing it.
Check a read-only tool result
Ask Muse to list the tools returned by NexusTrade and call fetch_portfolios with include_live=false and include_positions=false. Pass one returned portfolioId as portfolio_id to get_portfolio; inspect portfolio.portfolioId, portfolio.type and portfolio.strategies from the response. Check that identity against the account you intended to connect. An empty portfolio list can be valid for a new account; an authentication error or a missing tool result is not a successful check.
Keep approval enabled for account changes. Meta lets you change when Muse asks for approval in Settings. To disconnect a connector, open Settings, then Connectors.
Show the tools returned by the NexusTrade connector. Use an available read-only tool to read my account identity or list existing portfolios without updating them. Show the returned result and any error. Do not infer account data from web pages or create anything.Build a dated company brief
Use AAPL as a first test and request dated company data. Open the cited sources yourself and confirm issuer identity, reporting period and publication date. The brief should separate reported facts, interpretation and missing information. If a tool lacks a field, leave that field unresolved.
Using the NexusTrade connector, research AAPL. Show the company identity, dated fundamentals available from the tools, fiscal periods and source links. Follow primary filings where available. Separate reported facts from interpretation. State missing fields or failed requests. Return a research brief and the next question to investigate; do not place orders, activate a portfolio or launch a backtest.Review before testing a rule
Compare the returned fundamentals with their dates and linked filings. Resolve a missing source or an account mismatch before using the brief. If you decide to test a strategy, define explicit rules and assumptions in NexusTrade, then inspect the historical result separately from any forward paper observation.
Choose the task you want to finish
Use the research guide for a dated company brief, the backtest guide for one fixed historical candidate, or the paper guide to observe a separately identified simulated book. Each guide shows how to check the connection, retain the accepted operation ID and recover from a failed request.
Review a brokerage deployment separately
Public and Tradier have native NexusTrade account connection and strategy-port flows described below. Public also offers its own external MCP route. The Robinhood guide uses Claude Code with separate NexusTrade and Robinhood MCP servers; it does not imply that this client already has a verified native Robinhood connection. Broker account selection, order approval and a verified stop remain separate from paper observation.
Optional: check the account before owned-record changes
Optional: verify an owned portfolio before changes
Skip this step if you only want to inspect the public filing in the next step. Before reading or changing an owned portfolio, ask for a read-only list, inspect one returned ID with get_portfolio and compare its name, strategies and deployment type. An authenticated empty list is valid for a new account.
What you should see: For owned records, you have the intended account response or an authenticated empty response. Resolve an account mismatch before saving anything. Public filing inspection does not require an owned-portfolio read.
- Identity boundary
- A server list or public filing read does not verify access to your owned portfolios.
Use only NexusTrade read tools. Call fetch_portfolios, then get_portfolio with one returned portfolio ID. Report the ID, name, strategies and deployment type. If the authenticated list is empty, report that result. Do not create, edit, backtest, deploy or place orders.
No comments yet.