Agent workflows

Stock Event MCP Server for Company Event Briefings

Pineify provides a stock event MCP server that builds a bounded factual briefing for one exact US-listed company ticker. It covers recent company events and analyst actions from the previous 72 hours, plus scheduled earnings through the next 14 calendar days, with source metadata, coverage records, and explicit warnings.

MCP tool name
get-stock-event-context

Example prompt

Use Pineify get-stock-event-context at standard detail to build a sourced 72-hour event briefing for AMD and list any earnings scheduled in the next 14 calendar days.

Direct answer

What get-stock-event-context does

Call get-stock-event-context when an agent needs recent issuer releases, SEC filings, reported earnings, stock news, analyst actions, or the next scheduled earnings date for a known company. The tool accepts one bare ticker such as AMD or NVDA.

The recent window is fixed at 72 hours. The upcoming window starts on the current date in America/New_York and ends 14 calendar days later. The response states both windows so the agent does not have to infer the time boundary.

Recent events carry event times, snippets, and source metadata. Coverage records, the partial flag, and warnings show when data is empty, unavailable, invalid, missing a public source, conflicting, or truncated. The result is a latest available snapshot, not a live feed or a claim about what caused a stock move.

Contract

What the agent sends and receives

Inputs

  • `symbol`: one bare US-listed company ticker such as AMD or NVDA. The tool trims the value, converts it to uppercase, and rejects exchange prefixes.
  • `detail: "compact"`: the default. It can return up to 8 recent events, 2 sources per event, 4 analyst actions, and 3 upcoming earnings events.
  • `detail: "standard"`: increases the bounds to 12 recent events, 3 sources per event, 6 analyst actions, and 5 upcoming earnings events.

Structured output

  • The resolved company identity, market snapshot when available, retrieval time, fixed recent and upcoming windows, and schema version.
  • Recent events with type, title, time, bounded snippet, ticker list, optional earnings facts, and source metadata.
  • Recent analyst actions and upcoming earnings with available estimates, plus coverage status for each event section.
  • A partial flag and bounded warnings for unavailable data, invalid records, missing public sources, conflicts, or truncation.

Capabilities

Where this MCP tool fits

Collect recent company events

Returns bounded issuer releases, SEC filings, reported earnings, and stock news that fall inside the fixed 72-hour window.

Review recent analyst actions

Lists recent firms, actions, and previous or new grades when those records are available within the same 72-hour window.

Check upcoming earnings

Returns scheduled earnings through the next 14 calendar days with date, time status, fiscal period, and available estimates.

Audit sources and coverage

Exposes source kind, publisher, publication time, primary-source status, coverage records, warnings, and partial-result state.

Agent workflow

A bounded call from question to review

  1. 1

    Send one exact ticker

    Use a bare US-listed company ticker such as AMD. Do not send a company name, exchange prefix, or list of symbols.

  2. 2

    Choose the detail bound

    Keep compact for a short briefing. Use standard when more events, sources, analyst actions, or upcoming earnings records are useful.

  3. 3

    Read events with their windows

    Keep recent facts inside the returned 72-hour interval and upcoming earnings inside the stated 14-calendar-day window.

  4. 4

    Check provenance and gaps

    Review each recent event source, then inspect coverage, partial, and warnings before using the briefing in further research.

Prompt examples

Questions an agent can route to this tool

"Use Pineify get-stock-event-context at standard detail to build a sourced 72-hour event briefing for AMD and list any earnings scheduled in the next 14 calendar days."
"Get compact event context for NVDA. Separate issuer releases, SEC filings, earnings, stock news, and analyst actions that are actually present, then report coverage gaps."
"Check AAPL for recent company events and upcoming earnings. Keep every claim inside the returned windows and do not infer why the stock moved."

Operator notes

How I review the result

When I prepare an AMD briefing, I use standard detail if I need more than the compact limit of 8 recent events. I still leave empty sections empty instead of inventing a catalyst.

When I check NVDA, I keep the 72-hour recent window visible and distinguish primary issuer or SEC sources from publisher records. A source label does not prove that an event caused a price move.

When I review AAPL upcoming earnings, I use the returned America/New_York date window through the next 14 calendar days. I keep unknown timing and null estimates visible rather than guessing.

Boundaries to keep in the prompt

  • The recent window is fixed at 72 hours, and the upcoming earnings window is fixed at 14 calendar days. The tool does not accept custom dates or provide a historical archive.
  • The result is latest available and read-only. It is not a live news stream, and provider sections can be empty, unavailable, invalid, conflicting, or truncated.
  • Each call accepts one exact US-listed company ticker. It does not cover market-wide news, options flow, dark-pool activity, Congress trades, or trade execution.
  • Source URLs are attached to supported recent events when available. Earnings records can have no public URL, and analyst actions or upcoming earnings do not carry a per-record source link in this contract.
  • The tool reports event facts and analyst actions. It does not establish causation, label sentiment, predict stock prices, give personalized advice, or promise returns. It is an information tool, not investment advice.

Pineify MCP is an information and code-validation tool, not investment advice. It does not promise returns, place trades, or modify a portfolio. Review timestamps, source fields, code diagnostics, and risk assumptions before acting.

FAQ

Stock Event MCP Server for Company Event Briefings questions

Add get-stock-event-context to your AI workflow

Connect one remote Pineify MCP endpoint, then let your compatible AI client discover this tool with the rest of the read-only catalog.

Open MCP setup