Financial research with Codex: NVDA filings and fundamentals

1. Connect Codex in the workspace you will use

In the desktop app, open Settings, MCP servers and Add server. Name it nexustrade, choose Streamable HTTP and paste the endpoint below. Save, select Restart, then Authenticate and complete NexusTrade sign-in. In the composer, /mcp shows connected servers.

For CLI use, run the commands below in your research workspace, finish browser OAuth, then start codex. Desktop and CLI configuration is local; verify tools in the task where you will run the workflow.

codex mcp add nexustrade --url https://nexustrade.io/api/mcp
codex mcp login nexustrade
codex mcp list

2. Confirm access with an owned-resource read

Ask the client to discover tools and call fetch_portfolios, then pass one returned portfolioId as portfolio_id to get_portfolio. Inspect portfolioId, type, name, isActive and strategies; compare them with the same saved book in NexusTrade. Do not copy IDs from a demonstration. An empty list can be valid for a new account.

A tool-not-found error means revisit discovery. An authorization error means check the selected NexusTrade environment/account and OAuth connection. Do not ask the model to invent a replacement identifier.

Use only NexusTrade read tools. Call fetch_portfolios, then pass one returned portfolioId as the portfolio_id input to get_portfolio. Show portfolioId, type, name, isActive and complete strategies. Do not create, edit, backtest, deploy or place orders.

3. Request a bounded company brief

Create research/nvda-filings.md as the evidence record. Keep issuer identity, metric, unit, fiscal period, publication date, URL and the exact source passage together. The worked historical release below is a verification exercise, not the company's latest report.

Read NVDA issuer filings and the NVIDIA fiscal 2025 release published February 26, 2025. Extract annual revenue for FY2025 and FY2024 with units and fiscal end dates. Save a source table and the revenue-growth calculation in research/nvda-filings.md. Separate reported facts, arithmetic and interpretation. Do not submit research_topic, compute or orders until I approve the exact paid request.

4. Check a real NVIDIA revenue calculation

NVIDIA published its fiscal 2025 results on February 26, 2025 for the year ended January 26, 2025. Its GAAP table reports FY2025 revenue of $130,497 million and FY2024 revenue of $60,922 million.

The increase is $69,575 million. Dividing 69,575 by 60,922 gives about 114.2%, consistent with the release's rounded 114% growth. This supports a historical revenue-growth statement. It does not establish fair value or a future stock return. Keep the annual columns separate from the fourth-quarter figures.

Read filing references and statement periods

Call sec_edgar twice with the separate argument objects below. list_filings returns filing references; fundamentals reads inline XBRL metrics. Inspect filing dates, fiscal periods and units before comparing them with the historical release. The five recent filings may not include that older release. Missing evidence is a gap to resolve from the primary source, not permission to fill in a number.

Keep these reads separate from ingest_filings, which persists source text. For NVDA, annual periods preserve the twelve-month comparison.

{
  "ticker": "NVDA",
  "action": "list_filings",
  "forms": [
    "10-K",
    "10-Q"
  ],
  "limit": 5
}

{
  "ticker": "NVDA",
  "action": "fundamentals",
  "periods": "annual"
}

From a question to evidence

research_topic is asynchronous. Poll get_research_status with the same job ID instead of launching another billed research run for the same question.

No matching rows. Clear the filter to see all records.

5. Submit research only when the request is approved

If the primary sources leave a specific question unresolved, show the exact message for research_topic first. The accepted response includes researchJobId and status; save them before ending the session. A completed inline response may already contain citations. Otherwise pass the saved researchJobId as research_job_id to get_research_status.

PROCESSING means poll the same job. COMPLETED returns the report content and citations. FAILED returns an error to investigate. A second research_topic call starts another billed run; a missing response is not permission to duplicate it. If no saved ID exists, inspect the original tool response before considering another submission.

6. Finish the brief and recover an interrupted session

If the server is missing, inspect the selected local MCP configuration. If it requires OAuth, use Authenticate in the app or codex mcp login nexustrade in the CLI. After updating the desktop entry select Restart, then check /mcp. Reopen the saved artifact before continuing a new Codex task; a fresh conversation does not establish which operation was accepted.

Open research/nvda-filings.md and check each material claim against its link. Keep the original reported value and label each calculation. Leave absent/restated evidence explicit. For a newer-period brief repeat the source checks with the actual latest publication dates instead of carrying these historical figures forward.

The finished artifact should contain the source table, reproducible arithmetic, a bounded interpretation and the next unresolved question. It is a research brief, not a saved strategy or order instruction.

Costs and the next task

The local brief records your sources and calculations. A research_topic submission can consume credits, so review its exact question and your plan before starting it. Reuse the accepted job ID when polling or recovering a session. OAuth confirms account access; it does not verify the claims in a generated report.

For live deployment, review the separate broker guide, exact trading account and permissions. This client connection does not prove a native brokerage connector or a completed live workflow.

Continue exploring