Can I send a custom scanner expression?

No. The strict input accepts only six fixed technical-setup-v1 preset IDs. It does not accept Pine code, a DSL, custom thresholds, or custom scoring weights.

Does an empty match list mean the scanner failed?

Not necessarily. An empty list is a valid success when the response shows positive covered and evaluated counts and no required core failure.

Can AI predict stock prices with this MCP tool?

No. AI cannot predict stock prices with certainty, and this MCP tool does not promise future returns. It gives an agent bounded data or validation results that still require independent review, risk controls, and source checking.

Market analysis

Technical Setup Scanner MCP Tool for US Stocks

find-technical-setups scans one supported stock universe using one of six fixed `technical-setup-v1` presets. It evaluates canonical Pineify technical fields with bounded batching and returns up to 25 deterministically sorted matches with required evidence and current risk context, not entries, stops, targets, or arbitrary code.

Connect Pineify MCP View all MCP tools

MCP tool name

find-technical-setups

Example prompt

Use Pineify find-technical-setups to scan the S&P 500 for up to five 1d bullish-trend matches. Show coverage counts and every required evidence rule.

Direct answer

What find-technical-setups does

Supported universes are S&P 500, Nasdaq 100, Dow 30, and the Pineify US stock universe. The scanner intersects the requested universe with actual Pineify Alerts coverage for the requested timeframe.

A no-match response is a valid success when covered symbols were evaluated. Requested, deduped, covered, evaluated, eligible, and returned counts make that distinction visible.

Contract

What the agent sends and receives

Inputs

`universe`: `sp500`, `nasdaq100`, `dow30`, or `pineify-us-stocks`; defaults to `sp500`.
`setup`: one required fixed preset: `bullish-breakout`, `bullish-trend`, `bullish-pullback`, `bearish-breakdown`, `bearish-trend`, or `bearish-rally`.
`timeframe`: `15m`, `1h`, `4h`, or `1d`; defaults to `1d`. `limit` is an integer from 1 to 25 and defaults to 10.

Structured output

`technical-setups-v1` structured content and the exact `technical-setup-v1` preset methodology, thresholds, and stable tie-breaker.
Universe metadata, scan coverage/counts, and a bounded match list with score, direction, required/supporting evidence, price, ATR, relative volume, and source time.

Capabilities

Where this MCP tool fits

Run six versioned presets

Supports bullish breakout, trend, and pullback plus bearish breakdown, trend, and rally presets from one shared core registry.

Expose coverage counts

Reports requested, deduped, covered, evaluated, eligible, and returned counts with section source time and partial state.

Return deterministic evidence

Sorts eligible matches by score descending and symbol ascending, with required/supporting evidence, price, ATR, and relative volume.

Agent workflow

A bounded call from question to review

1
Choose a fixed universe and preset
Select one supported universe and one named setup rather than sending a custom expression.
2
Inspect coverage before matches
Confirm covered and evaluated counts are nonzero before interpreting an empty or short match list.
3
Verify required evidence
Read every required condition, observed value, rule, score, and source time before deeper company research.

Prompt examples

Questions an agent can route to this tool

"Use Pineify find-technical-setups to scan the S&P 500 for up to five 1d bullish-trend matches. Show coverage counts and every required evidence rule."

"Scan the Nasdaq 100 for 4h bearish-breakdown setups. Keep the deterministic order and explain why an empty match set can still be valid."

Operator notes

How I review the result

I treat a zero-match result as valid only when the scanner reports positive covered and evaluated counts.

I use a match as current technical evidence for follow-up research, not as a trade signal or execution instruction.

Boundaries to keep in the prompt

The tool accepts only four supported universes, four timeframes, six versioned presets, and a result limit from 1 to 25.
It rejects arbitrary Pine Script, DSL expressions, custom thresholds, custom weights, uploaded watchlists, entries, stops, targets, and backtests.
Coverage depends on current Pineify Alerts snapshots and may be partial. A setup describes current evidence, not future performance or 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.

MCP tool family