get a key
steadybase-$ skill company_why_now
toolcompany_why_now
groupEverything else
endpointhttps://mcp.steadybase.io/mcp

WHY THIS COMPANY, NOW. Returns the published why_now packages when the export carries them, with derived_from set to "why_now". When no package is published it does NOT invent one: it returns the 5 most recent public statements the company made, each with a verbatim quote and an https source_url, and marks the response derived_from="signals" so a caller can always tell an authored why-now from raw evidence. Read that marker before you quote this anywhere.

arguments
slug_or_ticker* string directory slug or canonical ticker
install
claude mcp add --transport http steadybase https://mcp.steadybase.io/mcp   --header "Authorization: Bearer $STEADYBASE_KEY"
call
curl -s https://api.steadybase.io/v1/mcp/call   -H "Authorization: Bearer $STEADYBASE_KEY" -H "Content-Type: application/json"   -d '{"tool":"company_why_now","arguments":{"slug_or_ticker":"..."}}'
contract
A quote comes with its receiptEvery returned statement carries the verbatim sentence and the URL it came from, and where the source is a transcript, the character offsets inside it. A statement with no receipt is not returned.
Empty is an answerWhen there is no sourced statement, the skill returns nothing. It does not summarise, infer, or fill the gap from general knowledge. Handle the empty case rather than retrying until something appears.
No personal contact dataNo email address, phone number, home address or personal social account is returned by any skill, at any tier. A person is a name, a professional role, a LinkedIn profile URL and the public record that puts them in that role.
No customer data crosses a keyA tenant-scoped skill reads only that tenant. Nothing about any customer appears on the public site or in another tenant answer.

/skills/

steadybase-$