Evaluate Executive Transition Risk With Claude MCP

An executive transition is not self-explanatory. A planned succession, an interim appointment, and a termination for cause may all produce the same headline: a new chief executive. The research questions are different.

This workflow is for analysts who already know that a leadership transition occurred and need to organize the evidence around it. It uses Claude with the FMP MCP Server to bring together primary disclosures, the last comparable reported quarter, and a narrow review of insider transactions. The result is a structured follow-up brief, not a risk score, an explanation of a board decision, or a forecast of future performance.

The distinction matters. A weak quarter does not establish why an executive left. A sale, award, gift, or vesting event does not establish an executive's view of the company. And an abrupt departure is not, by itself, evidence of a governance problem. The workflow preserves those boundaries so an analyst can see what the record supports and what needs further investigation.

Key takeaways

• Establish the transition from a contemporaneous filing or company announcement before adding financial or insider context.
• Use the most recent publicly reported fiscal quarter available before the announcement, then compare it with the same quarter a year earlier.
• Treat illustrative performance thresholds as a reason to investigate, not as evidence that results caused the leadership change.
• Review only the outgoing and incoming or interim executives' transactions in a defined window, and do not infer motives or Rule 10b5-1 status without filing support.
• Keep explicit governance disclosures separate from operating context and from the overall evidence status.

What this workflow can establish

The workflow separates five questions that are often collapsed into one:

Evidence layer	What it can establish	What it cannot establish on its own
Primary transition evidence	Who left, who was appointed, whether the role is interim or permanent, and the company's stated context	An undisclosed motive or private board rationale
Reported operating context	Revenue and operating-margin movement in the last comparable reported quarter	That performance caused the transition
Insider activity	The disclosed transactions returned for the named executives in the defined period	An executive's intent, conviction, or plan status without filing support
Governance evidence	Explicitly disclosed investigation, termination-for-cause, control, or compliance matters	A governance conclusion from an abrupt change alone
Evidence status	Whether the bounded review supports a confident result	Exhaustive coverage of every filing, transaction, or event

Use Review Required as an evidence status, not a transition type. It means a material fact, financial input, or transaction classification cannot be established reliably within the stated scope. It is an instruction to follow up, not a negative conclusion about the company or executive.

For timing, keep the board-action date, public-announcement date, filing date, and effective date separate. The announcement date is the first date the change was publicly disclosed in an official company announcement or public SEC filing. An SEC acceptance timestamp records acceptance by the SEC; it does not prove the exact moment a document became publicly accessible to every user or data provider.

Build the record in the right order

1. Establish the leadership event from primary sources

Start with the relevant 8-K, exhibit, or official company announcement. The SEC Filings by Symbol API is useful for locating filing metadata and direct document links, but narrative facts belong to the linked primary document, not the metadata response.

Record the outgoing executive, incoming or interim executive, public-announcement date, effective date, interim or permanent status, and the company's stated context. Classify the event as one of the following:

• Planned succession
• Interim appointment
• Abrupt departure
• Role consolidation
• Permanent replacement

If the sources describe the same event differently, preserve both descriptions and do not explain the difference by inference. Current executive records can help cross-check a present-day roster, but the Company Executives API is a current-state view. It should not be used to reconstruct a historical interim arrangement or the timing of a past departure.

2. Add reported operating context without rewriting history

For each company, use the last completed fiscal quarter that was publicly reported before the announcement date, plus the same fiscal quarter one year earlier. The Income Statement API supplies the dated revenue and operating-income inputs; verify the current-period values against the contemporaneous earnings release, 10-Q, 10-K, or comparable primary disclosure.

Calculate these values from unrounded reported inputs, then round only the displayed result:

• Revenue YoY: (Current revenue − prior-year revenue) ÷ prior-year revenue × 100
• Operating margin: Operating income ÷ revenue × 100
• Operating-margin change: Current operating margin − prior-year operating margin

For this example, an operating-review trigger occurs when revenue declines by at least 5% year over year or operating margin declines by at least 2 percentage points. These are illustrative review rules, not validated predictors and not a diagnosis of the reason for a transition.

Use reported GAAP operating income. Do not normalize the margin in this screen. If an earnings release identifies restructuring, impairment, store-closing, legal, or other unusual items, surface them as comparability context. The same applies to a 13-week versus 14-week quarter or another disclosed fiscal-period difference. The guide to aligning announcement dates, fiscal quarters, and reported results explains why those dates and periods cannot be treated as interchangeable.

If structured values and a contemporaneous primary disclosure cannot be reconciled, use the company-reported GAAP figure for the calculation only when the reporting basis is clear; otherwise return Review Required. Do not call either source erroneous without evidence.

3. Use insider activity as supporting context

Limit the search to the outgoing and incoming or interim executives, from 30 calendar days before through 30 calendar days after the public announcement. Use transaction date, not filing date, to determine whether a record falls inside the window.

Resolve the reporting person with the reporting-name search, then retrieve transactions with the Insider Trades API. Retain the executive, transaction date, code or type, share count, price where a numeric transaction price is actually reported, and filing link.

Classify only what the available record supports. A Code P purchase is a purchase with plan status unconfirmed unless the filing says more. A Code S sale is a sale with plan status unconfirmed unless the filing establishes a Rule 10b5-1 plan. Vesting, tax withholding, awards, and gifts remain their own categories. A reported weighted-average sale price is not an execution-price range, and a dividend-equivalent or reference amount is not automatically a transaction price.

This is intentionally a bounded check, not a broad insider-trading screen. If name matching, date coverage, or transaction interpretation is incomplete, return Review Required rather than reporting that no activity occurred.

4. Reserve governance findings for explicit disclosures

Look for explicit disclosure of misconduct, an investigation, termination for cause, financial-reporting or control issues, compliance concerns, or board dissatisfaction. An abrupt departure alone does not establish any of them.

The resulting brief should keep transition facts, operating-review context, insider context, governance evidence, and evidence status in separate fields. That separation is what keeps a compact workflow from turning correlation into causation.

Reconstruct the record with Claude and FMP MCP

Connect the FMP MCP Server in Claude's custom-connector settings using the connection details in the MCP Server documentation. Then use the following prompt with a defined watchlist or a known transition. It is designed to produce a focused research brief after an event is already identified; it does not discover and rank a mixed corporate-action feed.

Using the connected Financial Modeling Prep MCP server, create a compact executive-transition review for: - Walmart Inc. (WMT): Doug McMillon to John Furner - Intel Corporation (INTC): Pat Gelsinger departure to David Zinsner and Michelle Johnston Holthaus as interim co-CEOs - Kohl's Corporation (KSS): Ashley Buchanan departure to Michael Bender as interim CEO Purpose and scope This is a bounded research workflow for reviewing already-known executive transitions. It is not an exhaustive filing audit, investment recommendation, executive-compensation review, broad insider-trading screen, or corporate-action ranking model. Use FMP as the structured-data retrieval layer. Use primary company disclosures only where they are necessary to establish transition facts, reported-GAAP inputs, or transaction interpretation. Do not exhaustively paginate filings or repeatedly retry inaccessible sources. If a required evidence stream cannot be established reliably within this scope, set Evidence Status to Review Required and name the precise analyst follow-up. 1. Establish the transition Use the SEC Filings by Symbol data to locate relevant 8-Ks and linked exhibits, then use the official filing or company announcement as the source of transition facts. Use current executive data only as a current-state cross-check, never to reconstruct historical roles or interim status. For each company, report: - outgoing executive; - incoming or interim executive; - public-announcement date; - effective date, if disclosed; - interim or permanent status; - company-stated context; and - a descriptive primary-source link. Keep board-action date, public-announcement date, filing date, and effective date separate. Define Transition Announcement Date as the first public disclosure in an official company announcement or public SEC filing. Do not use an earlier board action or effective date if it was not yet public. Assign one Transition Type: Planned Succession, Interim Appointment, Abrupt Departure, Role Consolidation, or Permanent Replacement. If evidence is missing or conflicting, keep the transition type factual and set Evidence Status to Review Required. Do not infer a departure motive. For Intel, retain both source-specific descriptions: the Form 8-K's description of Gelsinger's departure and the company's public announcement. Do not infer why they differ. For Kohl's, establish from the primary disclosure whether it identifies termination for cause, an investigation, an interim CEO, and whether the company states that the action was unrelated to performance, financial reporting, or results of operations. For Michael Bender award transactions, do not treat a disclosed dividend-equivalent amount as a transaction price. If the Form 4 does not establish a numeric transaction price, report "No numeric transaction price reported." 2. Reproduce reported operating context Use quarterly Income Statement data. For each company, retrieve the last completed fiscal quarter publicly reported before the Transition Announcement Date and the same fiscal quarter one year earlier. Retain fiscal year, period, period-end date, filing date, revenue, and operating income. Cross-check current-period revenue and operating income against the contemporaneous earnings release, 10-Q, 10-K, or equivalent primary financial disclosure. Use comparative values in the same disclosure for the prior-year period when available. If the structured value and primary disclosure reflect different presentations, use the company-reported GAAP figure only when the basis is clear; note the difference without declaring either source erroneous. Otherwise set Evidence Status to Review Required. Calculate from unrounded inputs and display only final rounded values: - Revenue YoY = (current revenue - prior-year revenue) / prior-year revenue x 100 - Operating Margin = operating income / revenue x 100 - Operating-Margin Change = current operating margin - prior-year operating margin - Reporting Lag = Transition Announcement Date - current-quarter period-end date Apply this illustrative operating-review trigger only when all required financial inputs are established: - Revenue YoY declines by at least 5%; or - Operating margin declines by at least 2 percentage points year over year. Report either "Operating-review trigger under illustrative rule" or "No operating- review trigger under illustrative rule." This result is contextual. It does not establish that performance caused the transition. Use reported GAAP operating income. Do not calculate a normalized operating margin or add back restructuring, impairment, store-closing, legal, or other unusual items. Report such items, and any fiscal-period differences such as 13-week versus 14-week quarters, separately as analyst-review context. 3. Review insider activity For only the outgoing and incoming or interim executives, review the period from 30 calendar days before through 30 calendar days after the public announcement. Use transaction date, not filing date, for eligibility. Resolve the reporting person, then retrieve insider transactions. For each confidently matched transaction, retain executive, transaction date, transaction type or code, shares, price where a numeric transaction price is established, and a descriptive filing link. Classify transactions only when the available fields and, where necessary, the linked Form 4 support the classification. Permitted labels are: - Purchase (Code P), plan status unconfirmed - Sale (Code S), plan status unconfirmed - Rule 10b5-1 plan sale, only when filing evidence explicitly establishes the plan - Compensation-related award - RSU vesting or conversion - Tax withholding - Gift or other - Other or uninterpretable Do not infer Rule 10b5-1 status, discretion, or insider motive from a transaction pattern. Do not combine separate executives, dates, or codes. Preserve individual sale lines when a filing reports more than one line. For John Furner's November 20 sales, retain each reported line and its weighted-average price separately; identify any execution range separately. If a filing does not establish a numeric transaction price, report "No numeric transaction price reported" unless $0 is explicitly reported. If the required date coverage, identity match, or transaction interpretation is incomplete, set insider context and Evidence Status to Review Required rather than claiming that no activity occurred. 4. Identify explicit governance evidence Use primary disclosures to identify only explicitly stated misconduct, investigation, termination for cause, financial-reporting or control issues, compliance concerns, or another governance-sensitive circumstance. Do not infer a governance issue from an abrupt departure alone. 5. Return the review State the review cutoff date. Return one compact table with: | Company | Primary transition evidence | Transition Type | Reported operating context | Insider context | Explicit governance evidence | Evidence Status | Analyst follow-up | Use descriptive hyperlinks rather than displayed raw URLs. Keep transition facts, operating context, insider context, governance evidence, and Evidence Status separate. Follow the table with no more than three bullets that identify the most routine case, the clearest need for follow-up, and the most material limitation. Do not infer executive motives, insider motives, undisclosed causal relationships, or future company performance. Do not provide investment recommendations.

Worked examples: three different transition structures

The following historical cases show why the evidence streams should stay separate. They reflect a retrospective review with an information cutoff of September 26, 2026; insider activity is limited to the 30-day window on either side of each public announcement. The financial values use company-reported GAAP inputs verified against the corresponding primary financial disclosures. The operating-review rule is illustrative and does not explain a transition.

Company	Transition evidence	Reported operating context	Insider context in the bounded review	Research output
Walmart (WMT)	On November 14, 2025, Walmart's Form 8-K disclosed Doug McMillon's planned retirement and John Furner's appointment as permanent successor, effective February 1, 2026.	Q2 FY2026 revenue was $177.402B versus $169.335B a year earlier, up 4.76%. Operating margin was 4.11% versus 4.69%, down 0.58 percentage points; reporting lag was 106 days. No illustrative trigger. Reported results included $440M tied to certain legal matters and $150M of business-reorganization charges, shown as context only.	Filing-supported Rule 10b5-1 sales and a separately reported gift are not treated as a transition-specific signal.	Planned succession; routine continuity case.
Intel (INTC)	On December 2, 2024, Intel's Form 8-K said Pat Gelsinger resigned effective December 1, while the company announcement described his retirement and named David Zinsner and Michelle Johnston Holthaus interim co-CEOs.	Q3 2024 revenue was $13.284B versus $14.158B, down 6.17%. Operating margin was -68.18% versus -0.06%, down 68.12 percentage points; reporting lag was 65 days. Disclosed restructuring and impairment-related charges require separate interpretation.	A purchase and a Code S sale had plan status unconfirmed; later activity was compensation-related vesting and withholding. None establishes motive.	Interim appointment with an illustrative operating-review trigger; preserve the source wording difference.
Kohl's (KSS)	On May 1, 2025, Kohl's CEO-transition announcement disclosed Ashley Buchanan's termination for cause after an outside-counsel investigation and Michael Bender's interim appointment, following April 30 board action. The company stated that the action was unrelated to performance, financial reporting, and results of operations.	Q4 FY2024 revenue was $5.397B versus $5.956B, down 9.39%. Operating margin was 2.33% versus 5.02%, down 2.69 percentage points; reporting lag was 89 days. The comparison covers a 13-week current quarter and 14-week prior-year quarter; the current period also included $76M of impairments, store-closing, and other costs.	The bounded review did not establish a Buchanan transaction. Bender's identified transactions were compensation-related awards or withholding, not a transition-specific signal.	Explicit governance evidence plus an illustrative operating-review trigger; do not treat the operating result as the stated reason for the termination.

The cases lead to different follow-up questions. Walmart's record points to continuity. Intel's record requires a careful reading of its source-specific language and reported operating pressure without assigning causality. Kohl's requires governance follow-up because the company explicitly disclosed an investigation and termination for cause, while its own disclosure separates that action from company performance.

When to pause the workflow and investigate

Return Review Required when a key fact cannot be substantiated within the scoped review. Common examples include:

• the filing and official announcement give incompatible timing or role descriptions;
• the last reported quarter cannot be shown to have been public before the announcement;
• reported-GAAP financial inputs cannot be reconciled to the primary disclosure;
• fiscal-period differences make the comparison less informative than the label alone suggests;
• an insider cannot be matched confidently, or a Form 4 is needed to interpret a transaction; or
• the company gives limited, conflicting, or no explanation for a sudden leadership change.

Mixed corporate-action monitoring is a different job. If the task is to discover and prioritize executive changes alongside offerings, dividends, acquisitions, and other events, use a separate corporate-action escalation workflow. This transition review begins after a specific leadership event is already known.

From leadership change to a focused research brief

An executive-transition review is strongest when it starts with the company record, adds dated reported context, and leaves uncertain evidence visible. Claude can organize that work through FMP MCP, but the analyst remains responsible for deciding what changes the research view and what requires direct source review.

For a known transition, connect the FMP MCP Server, run the bounded prompt, and use the analyst-follow-up field in the resulting brief as the handoff to the next piece of research. If the next question is how a confirmed event changes market-data interpretation, the analysis belongs in an event-risk review of prices, volume, and volatility, not in the transition classification itself.

Frequently asked questions

What does this executive-transition workflow evaluate?

It organizes evidence around an already-known leadership change: the transition facts, the latest comparable reported operating results, a limited executive-specific insider review, explicit governance disclosures, and any outstanding analyst follow-up. It does not predict the outcome of the transition.

Can weak financial performance establish why an executive left?

No. Reported revenue and operating-margin changes provide context only. They can trigger further review under a stated rule, but they do not establish causality unless the company explicitly connects performance to the leadership change.

Why must primary filings and company announcements establish transition facts?

Structured data can locate documents and provide useful dates, but leadership status, stated rationale, investigation details, and effective dates are narrative facts. Those details should come from the contemporaneous filing, exhibit, or official company announcement.

How should insider transactions be used in a leadership-transition review?

Use them as supporting context for the named executives in a defined period around the announcement. Preserve transaction type, date, shares, price where reported, and filing source. Do not infer motive, discretion, or Rule 10b5-1 status unless the filing expressly supports it.

When should the workflow return Review Required?

Use Review Required when a core transition fact, reported-GAAP input, executive identity match, date window, or transaction classification cannot be established reliably within the bounded review. The result should name the exact source or question an analyst needs to check next.