exec_changes
Pack: exec-changes · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/exec_changes for the schema, then POST the same URL with its arguments for the data.
Executive and director appointments/departures for ONE company, from public filings: SEC 8-K Item 5.02 and Form 3 (initial ownership) for a US-listed company, or Companies House officer appointments/resignations for a UK company. A ticker/CIK input is US-only; a UK Companies House number is UK-only; a plain name tries BOTH registries but the UK leg only counts a hit whose name actually matches the query (no unrelated-namesake merges). If the name genuinely resolves in BOTH registries, the response has separate us/uk groups instead of one flat events list — the two are never merged, since that would misread as one company’s history. Each event: {date, person, role, change: appointed|departed|role_change, source, filing_url, excerpt, extraction}. US 8-K events carry a deterministic excerpt of the Item 5.02 text plus an explicit extraction status (“ok”, “ok (person/role not extracted — read the excerpt)”, or “failed:
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
company | string | yes | Company name, US stock ticker, SEC CIK, or UK Companies House number (“Acme Corp”, “AAPL”, “320193”, “SC123456”, “07098618”). A ticker-shaped input (“GD”, “AAPL”) or a bare CIK never queries Companies House. A plain name tries both registries and validates any UK match by name before accepting it. |
since | string | no | Earliest event date, ISO (YYYY-MM-DD). Defaults to 180 days ago. |
limit | number | no | Max events to return (default 20, max 50). |
Example call
Arguments
{
"company": "TALO",
"since": "2026-09-01"
}
curl
curl -X POST https://gateway.pipeworx.io/exec-changes/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"exec_changes","arguments":{"company":"TALO","since":"2026-09-01"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('exec_changes', {
"company": "TALO",
"since": "2026-09-01"
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the exec-changes pack
{
"mcpServers": {
"exec-changes": {
"url": "https://gateway.pipeworx.io/exec-changes/mcp"
}
}
}
See Getting Started for client-specific install steps.