Crypto ticker+timeframe → compact market-state brief (patterns, S/R, regime). Not advice.
Connect Patternfetch to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Crypto ticker+timeframe → compact market-state brief (patterns, S/R, regime). Not advice. The patternfetch mcp server is what makes that connection.
A detector that only reports double_top, confidence 0.92 tells an agent nothing about whether that pattern has ever meant anything. patternfetch attaches an evidence block to each detected pattern:
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
brief — Market-state report for one ticker + timeframe: compact candles, patterns with base rate and lift, support/resistance, regime, RSI/EMA, one-linemulti — One brief per timeframe (default 1h, 4h, 1d) plus a cross-timeframe alignment read that spells out agreement or divergence, e.g. 1h up / 4h up / 1ddelta — Only what changed since the last brief for that ticker + timeframe — trend flips, new patterns, RSI-state changes. Returns changed: false whenanalogs — Historical windows whose shape resembles current price action, with the full distribution of what followed: win rate, median, mean, min, max and nscan — Screener over a curated universe of liquid US large-caps, core and sector ETFs and major crypto pairs. Filter by asset class, regime, pattern andcapabilities — Supported assets, timeframes, endpoints, limits and pricing. No inputConfiguration is passed through the environment: PATTERNFETCH_API_KEY, PATTERNFETCH_MCP_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at patternfetch on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Patternfetch's toolset — brief, multi, delta and 3 more — is a fair guide to whether it matches your workflow. It is maintained by MarvinRey7879; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Patternfetch's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| brief | Market-state report for one ticker + timeframe: compact candles, patterns with base rate and lift, support/resistance, regime, RSI/EMA, one-line summary. |
| multi | One brief per timeframe (default 1h, 4h, 1d) plus a cross-timeframe alignment read that spells out agreement or divergence, e.g. 1h up / 4h up / 1d down. |
| delta | Only what changed since the last brief for that ticker + timeframe — trend flips, new patterns, RSI-state changes. Returns changed: false when nothing material moved. |
| analogs | Historical windows whose shape resembles current price action, with the full distribution of what followed: win rate, median, mean, min, max and n over a fixed forward horizon. |
| scan | Screener over a curated universe of liquid US large-caps, core and sector ETFs and major crypto pairs. Filter by asset class, regime, pattern and minimum base rate; rows return ranked by base rate with 95% CI. Precompute |
| capabilities | Supported assets, timeframes, endpoints, limits and pricing. No input. |
{
"mcpServers": {
"patternfetch": {
"command": "npx",
"args": ["-y", "patternfetch"],
"env": {
"PATTERNFETCH_API_KEY": "your-value",
"PATTERNFETCH_MCP_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PATTERNFETCH_API_KEY | Credential the server authenticates with. | Yes |
| PATTERNFETCH_MCP_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.