Research MSFT with VS Code Copilot

1. Connect the tools in your workspace

Open NexusTrade Developers and choose Add to VS Code, or run MCP: Add Server from the Command Palette. Select the hosted HTTP server and save a portable .mcp.json at the workspace root. Trust/start the server, complete NexusTrade OAuth and open Chat > Configure Tools to enable the required tools.

This is the Copilot MCP connection. The Codex extension has a separate setup. Existing .vscode/mcp.json uses servers rather than the portable mcpServers object below. Inspect the server error and pending sign-in if tools fail to appear.

Portable workspace configuration

{
  "mcpServers": {
    "nexustrade": {
      "type": "http",
      "url": "https://nexustrade.io/api/mcp"
    }
  }
}

2. Check the returned account tools

The result is a paginated object with portfolios, total and totalPages. Walk pages when necessary. A new account may return an empty list. Keep authentication errors and missing results separate. Do not infer a successful connection from a tool list alone.

Use fetch_portfolios with the JSON below. Read a portfolioId returned by that call with get_portfolio, setting its portfolio_id argument to the same value. Compare the name, type and strategies with the intended NexusTrade account. If no portfolio exists, keep the empty result and use the company data request next. Do not create anything during this check.

{
  "include_paper": true,
  "include_live": false,
  "include_chat_portfolios": true,
  "include_positions": false,
  "limit": 20,
  "page": 1
}

3. Retrieve filings before interpreting the company

Expected output is dated filing rows or annual metric records, rather than a generic stock recommendation. If the source has no matching fiscal period, leave the comparison unresolved and follow the issuer link below.

Start the current company brief with the latest filed annual and quarterly periods returned by the tool. The historical worked example below checks your reconciliation method; it does not replace that current filing review.

Call sec_edgar with each argument object below. The first requests filing rows; the second requests inline annual XBRL metrics. Keep filing dates, accession identifiers and links returned by the tool. Do not use ingest_filings for this read-only check.

{
  "ticker": "MSFT",
  "action": "list_filings",
  "forms": [
    "10-K",
    "10-Q"
  ],
  "since": "2025-01-01",
  "limit": 10
}

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

Worked source check: Microsoft FY2025

The Microsoft release published 2025-07-30 reports the fiscal year ended 2025-06-30. The statement values below are USD millions. This is a fixed historical source example, not the newest company report.

Dividing operating cash flow by revenue gives 48.33% for this annual period. That cash conversion ratio measures operating cash flow relative to reported sales. It is not free cash flow, a stock-return forecast or a reason to buy. A later release may restate an earlier value; retain the original source and explain any mismatch.

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

Historical issuer-reported values, not trading performance.

4. Reconcile the tool values with the actual statement

Check the cash-flow statement period: a nine-month year-to-date value cannot be compared with a twelve-month revenue value. Normalize millions versus dollars before computing a ratio. Do not add a company metric to a price rule unless its historical availability is represented.

Use the returned MSFT filing rows and annual XBRL metrics. Reconcile FY2025 revenue 281,724 and operating cash flow 136,162, both USD millions, for the year ended 2025-06-30, against this source: https://www.microsoft.com/en-us/Investor/earnings/FY-2025-Q4/press-release-webcast. Build a table with metric, raw value, unit, start/end dates, fiscal period, source publication date and source URL. Separate any quarterly, year-to-date, annual and restated records. Explain mismatches rather than choosing the most favorable number. Return research/MSFT.md, strategies/msft-sma-v1.json and experiments/msft-sma-v1.md in your workspace. Do not create, backtest, deploy or trade a portfolio.

5. Resolve one remaining question without duplicate research

If the brief needs broader evidence, review a specific research_topic message before submitting it. Preserve researchJobId from the accepted response and poll get_research_status with research_job_id set to that exact returned value. PROCESSING means poll the same job; COMPLETED supplies report/citations; FAILED supplies an error. Another research_topic call starts another billed run.

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.

Continue exploring