---
name: noxstock
description: >-
  Structured context for US-listed stocks and ETFs (NYSE/NASDAQ): symbol search,
  snapshot, valuation, fundamentals, earnings, dividends, technicals, price action,
  history, compare, SEC filings, and insider Form 4 activity. Use over hosted MCP or
  REST when a task needs quote, performance, valuation, financial, technical, SEC, or
  insider data for a US ticker. Not for trading, options, real-time L2, or non-US equities.
---

# noxstock

## Use it for

US-listed stock and ETF context: resolve a company or fund name to a symbol, then
pull snapshot, valuation, fundamentals, earnings, dividends, technicals, price action,
price history, a 2-4 symbol compare, SEC filings (list, metadata, section text), or the
trailing 90-day insider Form 4 rollup. Coverage is NYSE and NASDAQ listings.

## Don't use it for

Trading or order execution, exchange-grade real-time or L2/order-book data, options,
futures, crypto, FX, non-US equities, analyst consensus or price targets, earnings-call
transcripts, news, ownership/13F positions, or investment advice. If asked for any of
these, say "not available from noxstock."

## Setup

Prefer hosted MCP. Set `NOXSTOCK_API_KEY` first (create a key at
https://noxstock.com/dashboard/keys), then add the server:

```json
{
  "mcpServers": {
    "noxstock": {
      "url": "https://api.noxstock.com/mcp",
      "headers": { "X-API-Key": "$NOXSTOCK_API_KEY" }
    }
  }
}
```

Smoke-test: confirm the `noxstock_*` tools loaded, then call
`noxstock_snapshot({ "symbol": "AAPL" })`. A success returns `{ "data": ... }` with
`freshness` and `as_of`. MCP tool arguments use native JSON types — lists are arrays
(`["10-K","10-Q"]`), not comma-separated strings.

REST fallback (same key, every request carries the header):

```bash
curl -sS "https://api.noxstock.com/v2/snapshot?symbol=AAPL" \
  -H "X-API-Key: $NOXSTOCK_API_KEY"
```

MCP is read-only and calls REST under the hood. When the two disagree, REST/OpenAPI is
the source of truth.

## Plans

A Free key calls search, coverage, snapshot, and valuation only; every other route
returns `PLAN_UPGRADE_REQUIRED`. Starter and Builder keys reach all routes and tools.
See https://noxstock.com/docs/reference/plans-and-limits.

## Default call sequence

1. If the user names a company or fund, call search to resolve the symbol.
2. Call coverage before storing, batching, or deeply analyzing a symbol.
3. Call snapshot for most single-symbol questions.
4. Add only what the question needs: valuation, fundamentals, compare (2-4 tickers),
   filings list -> filing -> filing section for SEC text, insider for Form 4 activity,
   technicals + price-action for trend and timing, history only for a time series.

## Output rules

- Answer first, then the few supporting facts, then freshness, then the calls you made.
- Parse the envelope: success is top-level `data`; failure is top-level `error` with
  `code`, `message`, and `retryable`. Retry only when `retryable` is true and honor
  `Retry-After`.
- Preserve every value as returned — units, signs, `_pct`, `_usd`, fiscal periods,
  accessions, filing dates, `as_of`, `freshness`, `market_status`, notices, and
  null/unavailable reasons. Never round away a sign or invent precision.
- Treat `freshness: "unsupported"` and `available: false` reasons as facts. Say "not
  available from noxstock" instead of guessing; do not retry these states.
- Summarize SEC risk/MD&A/business/press-release content only from the returned filing
  section text. Do not blend in news, consensus, the web, or memory.
- Report data; do not advise. No buy/sell/hold verdict, price target, or trade
  instruction. Keep the API key server-side — never in client code, logs, or prompts.

## Go deeper

- Agent recipes (prompt -> calls -> answer): https://noxstock.com/docs/agents/recipes
- Choose the right endpoint: https://noxstock.com/docs/guides/choose-endpoints
- Error codes and retry policy: https://noxstock.com/docs/reference/error-codes
- Hosted MCP setup: https://noxstock.com/docs/mcp/hosted
- API reference: https://noxstock.com/docs/api-reference/overview