io.github.Nikoble1926/kraken-signals-mcp
NPM · KRAKEN-SIGNALS-MCP · SCANNED SEP 22
Kraken crypto signals via x402: free preview + paid USDC-on-Base signals, regime & indicators
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 128 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 501 tokens (~71/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the io.github.Nikoble1926/kraken-signals-mcp server?
io.github.Nikoble1926/kraken-signals-mcp runs locally as an npm package, launched with npx -y kraken-signals-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kraken-signals-mcp
claude mcp add nikoble1926-kraken-signals-mcp -- npx -y kraken-signals-mcp
{
"mcpServers": {
"nikoble1926-kraken-signals-mcp": {
"command": "npx",
"args": [
"-y",
"kraken-signals-mcp"
]
}
}
} {
"servers": {
"nikoble1926-kraken-signals-mcp": {
"command": "npx",
"args": [
"-y",
"kraken-signals-mcp"
]
}
}
} codex mcp add nikoble1926-kraken-signals-mcp -- npx -y kraken-signals-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nikoble1926-kraken-signals-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"kraken-signals-mcp"
],
"enabled": true
}
}
} openclaw mcp add nikoble1926-kraken-signals-mcp --command npx --arg -y --arg kraken-signals-mcp
mcp_servers:
nikoble1926-kraken-signals-mcp:
command: "npx"
args: ["-y", "kraken-signals-mcp"] {
"McpServers": {
"nikoble1926-kraken-signals-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"kraken-signals-mcp"
]
}
}
} assistant mcp add nikoble1926-kraken-signals-mcp -t stdio -c npx -a -y kraken-signals-mcp
{
"mcpServers": {
"nikoble1926-kraken-signals-mcp": {
"command": "npx",
"args": [
"-y",
"kraken-signals-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 +6
- Source repository: fail → pass ▲ security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/kraken-signals-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 128 packages
| Packages resolved | 128 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_backtest ~126
Paid ($0.25 USDC): walk-forward replay of the live multi-timeframe strategy over recent 1m history. Returns win-rate + average forward return per BUY/SELL signal so an agent can measure recent edge before subscribing.
| Name | Type | Req | Description |
|---|---|---|---|
| forward | integer | – | Forward window in 1m bars to score each signal against (5-120) |
| pair | string | – | Kraken */USD pair, e.g. BTC/USD, ETH/USD |
| step | integer | – | Walk-forward step in 1m bars (1-15). Smaller = denser sample but slower. |
No output schema declared.
No examples provided.
get_history ~62
Paid ($0.05 USDC): revealed historical signal snapshots (commit-reveal hash chain). Returns past BUY/SELL/HOLD calls with their verifiable hashes; the latest snapshot is withheld.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many past snapshots (1-100) |
No output schema declared.
No examples provided.
get_indicators ~104
Paid ($0.005 USDC): atomic TA indicators (RSI, EMA, MACD, ATR, Bollinger, volume) for a pair/timeframe. Cheap high-frequency poll endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional: return only one indicator (e.g. rsi14, ema50, macd_hist) |
| pair | string | – | Kraken */USD pair, e.g. BTC/USD, ETH/USD |
| tf | string | – | Candle timeframe |
No output schema declared.
No examples provided.
get_regime_changed ~83
Paid ($0.02 USDC): current market regime (RISK_ON/RISK_OFF) from a provable chain + whether it changed since the regime you last saw. Cheap poll endpoint to react to regime flips.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Regime you last saw (e.g. RISK_ON). If omitted, response reports the current regime only. |
No output schema declared.
No examples provided.
get_signal ~49
Paid ($0.01 USDC): trading signal + confidence for one pair. Any active Kraken */USD pair.
| Name | Type | Req | Description |
|---|---|---|---|
| pair | string | – | e.g. BTC/USD, ETH/USD, SOL/USD |
No output schema declared.
No examples provided.
get_signal_preview ~32
FREE sample: current BTC/USD signal direction (BUY/SELL/HOLD), no payment, no wallet key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_top_signals ~45
Paid ($0.10 USDC): market scan — strongest BUY/SELL signals across major pairs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many top signals (1-10) |
No output schema declared.
No examples provided.
What is the io.github.Nikoble1926/kraken-signals-mcp server?
io.github.Nikoble1926/kraken-signals-mcp is listed in the public MCP registry as io.github.Nikoble1926/kraken-signals-mcp. Kraken crypto signals via x402: free preview + paid USDC-on-Base signals, regime & indicators. This page covers its npm package (kraken-signals-mcp).
Is the io.github.Nikoble1926/kraken-signals-mcp server safe to use?
io.github.Nikoble1926/kraken-signals-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 io.github.Nikoble1926/kraken-signals-mcp server expose?
io.github.Nikoble1926/kraken-signals-mcp exposes 7 tools: get_signal_preview, get_signal, get_top_signals, get_history, get_regime_changed, and 2 more. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.
Is the io.github.Nikoble1926/kraken-signals-mcp server still maintained?
io.github.Nikoble1926/kraken-signals-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Nikoble1926/kraken-signals-mcp server under?
io.github.Nikoble1926/kraken-signals-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.