Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

patternfetch

REMOTE · PATTERNFETCH.COM

US stocks, ETFs, crypto → compact brief: patterns, S/R, regime + base rates vs baseline. Not advice.

Available components

0 this week 92 Trust /100

Last scanned (12 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2620 tokens (~436/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://patternfetch.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=patternfetch.com CN=YE2,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 697bb08c1a0eba5b7c0a5e04d5a924d000a
SANs: patternfetch.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of patternfetch.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
patternfetch.com. DS published 27055 13 Verified
patternfetch.com. Verified address RRset verified with the apex keys
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://patternfetch.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://patternfetch.com/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://patternfetch.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://patternfetch.com/mcp
Authorisation server https://patternfetch.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://patternfetch.com/mcp Verified 200
http (plaintext) http://patternfetch.com/mcp HTTPS enforced 308 https://patternfetch.com/mcp
MCP tools · 6 exposed · ~2,620 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
patternfetch_analogs ~422

Find earlier windows IN THE SAME SERIES whose shape resembles the current price action and return the FULL distribution of what followed (win-rate, median, min, max, n) over a fixed forward horizon. Parameters: window = how many recent bars form the shape being matched (default 32); horizon = how many bars forward each match is measured over (default 20). WHEN: an agent wants the historical spread of outcomes after a similar-looking setup, including how wide and how uncertain that spread is. WHEN NOT: you want the current technical picture (use brief), you want to find candidates across the market (use scan), or you need one expected value — this deliberately returns a distribution, not a point estimate. NOT a prediction, NOT a backtest of a strategy; past distribution does not guarantee future results. Example: {"ticker":"ETH/USDT","timeframe":"1d"}. Impersonal data, not advice.

NameTypeReqDescription
horizoninteger–Number of bars forward over which the outcome after each match is measured. Default 20.
marketstring–Optional asset-class override. Omit and it is inferred from the ticker: a "BASE/QUOTE" pair is crypto, a plain symbol is a US stock/ETF.
tickerstringyesSymbol to analyse. US stock or ETF like "AAPL" / "SPY", or a crypto spot pair like "BTC/USDT". Always spell crypto as a pair: a bare "BTC" or "ETH" is a real US-listed ETF, NOT the coin, and it will…
timeframestringyesBar size. One of 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w. Coverage differs per asset class — see the capabilities tool.
windowinteger–Number of recent bars forming the shape matched against history. Default 32.

No output schema declared.

No examples provided.

patternfetch_brief ~409

Get a token-compact market-state brief for a stock, ETF, or crypto ticker + timeframe. Returns compact candles, detected chart/candlestick patterns with geometric confidence AND a backtested historical base rate (how often that pattern+timeframe+confidence-band actually resolved its way), support/resistance levels, trend/regime, and interpreted indicators (RSI/EMA state) plus a one-line summary. Covers US stocks/ETFs (split & dividend adjusted, delayed/EOD) and crypto spot (realtime). WHEN: an agent needs the current technical picture of a market without dumping raw OHLCV into context (saves tokens, avoids numeric hallucination). WHEN NOT: you need order execution or portfolio advice. Examples: {"ticker":"AAPL","timeframe":"1d"}, {"ticker":"BTC/USDT","timeframe":"4h"}. Output is impersonal market data, NOT investment advice.

NameTypeReqDescription
limitinteger–How many recent bars to analyse: integer >= 20, capped at 1000, default 200. Fewer bars = fewer tokens.
marketstring–Optional asset-class override. Omit and it is inferred from the ticker: a "BASE/QUOTE" pair is crypto, a plain symbol is a US stock/ETF.
tickerstringyesSymbol to analyse. US stock or ETF like "AAPL" / "SPY", or a crypto spot pair like "BTC/USDT". Always spell crypto as a pair: a bare "BTC" or "ETH" is a real US-listed ETF, NOT the coin, and it will…
timeframestringyesBar size. One of 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w. Coverage differs per asset class — see the capabilities tool.

No output schema declared.

No examples provided.

patternfetch_capabilities ~163

Return patternfetch's own capability matrix: which asset classes are covered (US stocks, ETFs, crypto spot), the data source and delay for each, the supported timeframes, the endpoint list, the per-call prices and tier limits, and the product version. Takes no arguments and returns the same static self-description on every call — it contains NO market data (no quotes, candles, patterns or base rates). WHEN: once at the start of a session, to learn which asset classes and timeframes are supported before calling brief/multi/delta/analogs/scan, instead of guessing and getting a validation error. WHEN NOT: you already know the ticker and timeframe are supported (go straight to brief), or you want actual market data (this returns none).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

patternfetch_delta ~318

Get only what CHANGED since your last brief for a ticker+timeframe (trend flips, new patterns, RSI-state changes). WHEN: an agent polls the same market repeatedly and wants minimal tokens — call brief once, then delta on each later poll. WHEN NOT: first look at a market (use brief). Returns changed=false when nothing material changed. Example: {"ticker":"BTC/USDT","timeframe":"4h"}. Impersonal data, not advice.

NameTypeReqDescription
limitinteger–How many recent bars to analyse: integer >= 20, capped at 1000, default 200. Fewer bars = fewer tokens.
marketstring–Optional asset-class override. Omit and it is inferred from the ticker: a "BASE/QUOTE" pair is crypto, a plain symbol is a US stock/ETF.
tickerstringyesSymbol to analyse. US stock or ETF like "AAPL" / "SPY", or a crypto spot pair like "BTC/USDT". Always spell crypto as a pair: a bare "BTC" or "ETH" is a real US-listed ETF, NOT the coin, and it will…
timeframestringyesBar size. One of 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w. Coverage differs per asset class — see the capabilities tool.

No output schema declared.

No examples provided.

patternfetch_multi ~389

Get a multi-timeframe market-state view for one stock, ETF, or crypto ticker in a single call: a token-compact brief for each requested timeframe (default 1h, 4h, 1d) PLUS a cross-timeframe alignment read — whether the trends across timeframes agree or diverge, with the split spelled out (e.g. "1h up / 4h up / 1d down"). WHEN: an agent wants to know if a setup is confirmed across horizons or conflicting between them, without making 3 separate brief calls. WHEN NOT: you only care about one timeframe (use brief). The alignment/divergence is impersonal DESCRIPTIVE data, not a signal to act on. Example: {"ticker":"BTC/USDT","timeframes":["1h","4h","1d"]}. Not investment advice.

NameTypeReqDescription
limitinteger–How many recent bars to analyse: integer >= 20, capped at 1000, default 200. Fewer bars = fewer tokens.
marketstring–Optional asset-class override. Omit and it is inferred from the ticker: a "BASE/QUOTE" pair is crypto, a plain symbol is a US stock/ETF.
tickerstringyesSymbol to analyse. US stock or ETF like "AAPL" / "SPY", or a crypto spot pair like "BTC/USDT". Always spell crypto as a pair: a bare "BTC" or "ETH" is a real US-listed ETF, NOT the coin, and it will…
timeframesarray–Bar sizes to compare, at most 4, e.g. ["1h","4h","1d"]. Defaults to ["1h","4h","1d"] when omitted.

No output schema declared.

No examples provided.

patternfetch_scan ~919

Scan US stocks, ETFs, and crypto for tickers currently in a given regime or showing a chart/candlestick pattern, RANKED by the honest backtested base rate + 95% CI — discovery, NOT lookup. This is the screener: instead of asking about one ticker you already know, ask "which tickers right now are in an uptrend / printing a double_bottom, and which of those has the strongest historical base rate?" and get a ranked shortlist back. Precomputed daily over a curated universe (liquid US large-caps + core/sector ETFs + major crypto pairs) so it is fast and cheap. Filters (all optional): assetClass ("stock"|"crypto"|"all"), regime ("up"|"down"|"range"), pattern (e.g. "double_bottom","double_top","head_and_shoulders","bullish_engulfing","bearish_engulfing","hammer"), minLift (-1..1 in rate points, e.g. 0.02 = keep only patterns beating their OWN pattern-free baseline by >= 2pp; 0 = at or above baseline), minBaseRate (0..1, drop tickers whose top pattern base rate is below this), tf, limit. PREFER minLift over minBaseRate: a raw base rate is not comparable across bullish and bearish rows, so minBaseRate:0.55 mostly returns bullish patterns in a rising universe before any of them carries information, whereas minLift returns the ones that measurably add something. Rows with no baseline in the evidence table are excluded by any minLift (absence of a lift is not a lift of 0). Each row: {sym, tf, assetClass, regime, pattern, baseRate, ci95, n, scope, confidence, asOf} PLUS the drift-free comparison {baseline, lift, liftCi95, liftReading} — baseline is the direction-matched rate with no pattern present, lift is baseRate minus that baseline, and liftReading says whether the difference is distinguishable from zero at all ("above-baseline" | "below-baseline" | "indistinguishable-from-baseline"). Read lift, not baseRate, when comparing a bullish row against a bearish one: in a rising universe a bullish pattern starts ahead before it carries any information. Ranked by baseRate desc, the…

NameTypeReqDescription
assetClassstring–Restrict the scanned universe. Default "all".
limitinteger–Maximum rows to return: integer in [1,500], default 50.
minBaseRatenumber–Number in [0,1]. Drop tickers whose top pattern base rate is below this threshold. CAUTION: a raw base rate is NOT comparable across bullish and bearish rows — in a rising universe a bullish pattern…
minLiftnumber–Number in [-1,1], in rate points (0.02 = 2pp). Drop tickers whose top pattern does not beat its OWN pattern-free baseline by at least this much. This is the drift-free filter and the one to reach for…
patternstring–Only return tickers whose top pattern is this one, e.g. "double_bottom", "double_top", "head_and_shoulders", "bullish_engulfing", "bearish_engulfing", "hammer".
regimestring–Only return tickers currently in this regime. Omit for any.
tfstring–Only return signals precomputed on this bar size. Omit to consider every precomputed timeframe.

No output schema declared.

No examples provided.

Install

How do I install the patternfetch MCP server?

patternfetch is a hosted endpoint at https://patternfetch.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · patternfetch.com

# add to Claude Code
claude mcp add --transport http marvinrey7879-patternfetch 'https://patternfetch.com/mcp'
Common questions

What is the patternfetch MCP server?

patternfetch is an MCP server listed in the public MCP registry as io.github.MarvinRey7879/patternfetch. US stocks, ETFs, crypto → compact brief: patterns, S/R, regime + base rates vs baseline. Not advice. This page covers its hosted endpoint (https://patternfetch.com/mcp).

Is the patternfetch MCP server safe to use?

patternfetch scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the patternfetch MCP server expose?

patternfetch exposes 6 tools: patternfetch_brief, patternfetch_multi, patternfetch_delta, patternfetch_analogs, patternfetch_scan, patternfetch_capabilities. Their descriptions and schemas cost roughly 2,620 tokens of context every time the server is loaded.

Does the patternfetch MCP server require authentication?

Yes. patternfetch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the patternfetch MCP server still maintained?

patternfetch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the patternfetch MCP server?

VerifyMCP ran 13 checks on patternfetch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.