Kraken Signals Mcp

io.github.Nikoble1926Published by GitHub account Nikoble1926v1.1.1Updated Oct 24, 2026

Kraken crypto signals via x402: free preview + paid USDC-on-Base signals, regime & indicators

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant Kraken crypto trading signals, from a free BTC/USD preview to paid USDC-on-Base signal, regime, history, backtest and R

What you can do
Get a free BTC/USD direction preview (BUY/SELL/HOLD) without any wallet key. Fetch a paid signal with confidence for any Kraken pair quoted in USD. Scan the market for the strongest signals across major pairs. Retrieve revealed historical signal snapshots with verifiable hashes and check the market regime (RISK_ON/RISK_OFF) and whether it changed. Run walk-forward backtests with win rate and average forward return, and read atomic technical indicators (RSI, EMA, MACD, ATR, Bollinger, volume) for a pair and timeframe.
When to use it
Useful when you want an assistant to pull crypto market signals, regime state, backtest statistics or technical indicators into a conversation. The free preview is enough to try it; the paid tools suit users willing to spend a few cents per call from a small USDC balance on Base.
Requirements
Runs locally over stdio, typically launched with npx from the npm package, so Node.js is needed. The free preview needs no key. Paid tools need EVM_PRIVATE_KEY, a Base wallet private key for a low-balance hot wallet holding USDC; RESOURCE_SERVER_URL optionally overrides the API base URL. Network access to the signals API is required.
Before you install
Paid tools spend real USDC on Base per call (from $0.005 to $0.25), so costs add up with use. EVM_PRIVATE_KEY is a wallet private key: use a dedicated throwaway hot wallet with a small balance, never a main wallet, and keep it only in local client config. Signals are described as educational, not financial advice. The optional RESOURCE_SERVER_URL can redirect requests to another endpoint.

Installation

In SourceWeft

  1. Open Kraken Signals Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Kraken Signals MCP

Wire Kraken Crypto Signals into Claude Desktop, Cursor, or any MCP client as tools. Ask your agent for a signal and it calls the tool; for the paid tools the bridge pays USDC on Base automatically via x402 and returns the result.

The get_signal_preview tool is free and needs no wallet key. The other tools cost a few cents per call and activate only when you set a Base wallet key.

Quick start (no clone, no build)

Add this to your client config and you're done — npx fetches and runs it:

Claude Desktop — Settings → Developer → Edit Config:

json
{  "mcpServers": {    "kraken-signals": {      "command": "npx",      "args": ["-y", "kraken-signals-mcp"]    }  }}

That gives you the free preview out of the box. To enable the paid tools, add a low-balance Base wallet key:

json
{  "mcpServers": {    "kraken-signals": {      "command": "npx",      "args": ["-y", "kraken-signals-mcp"],      "env": {        "EVM_PRIVATE_KEY": "0x<your-low-balance-base-wallet-private-key>"      }    }  }}

Cursor — Settings → MCP → Add new server, same command/args/env.

Restart the client, then ask: "Get the BTC signal preview" (free) or "Get the top crypto signals right now" (paid).

Tools

ToolCostDescription
get_signal_previewfreeCurrent BTC/USD direction (BUY/SELL/HOLD), no wallet key required
get_signal$0.01 USDCSignal + confidence for one pair (any Kraken */USD)
get_top_signals$0.10 USDCMarket scan — strongest signals across major pairs
get_history$0.05 USDCRevealed historical signal snapshots (commit-reveal) + verifiable hashes
get_regime_changed$0.02 USDCMarket regime (RISK_ON/RISK_OFF) + whether it changed since you last looked
get_backtest$0.25 USDCWalk-forward replay: win-rate + avg forward return per BUY/SELL signal
get_indicators$0.005 USDCAtomic TA indicators (RSI, EMA, MACD, ATR, Bollinger, volume) for a pair/timeframe

Paid mode (optional)

The paid tools need an EVM_PRIVATE_KEY: a Base wallet private key for a low-balance, dedicated hot wallet holding a little USDC — never your main wallet. Payments are gasless for the payer (the facilitator covers gas), so you mainly need a small USDC balance. Without the key, paid tools return a clear "set EVM_PRIVATE_KEY" message and the free preview keeps working.

RESOURCE_SERVER_URL is optional and defaults to https://signals.nsgoods.org.

Run from source (dev)

bash
cd mcpnpm installnpm run buildnode dist/server.js   # or: npm run dev

Security

  • The EVM_PRIVATE_KEY is yours (the buyer's) and stays local in your client config — it is never sent to the API. Use a throwaway hot wallet with only a small USDC balance.
  • For spend control, see the policy-check hooks in the official x402 MCP guide and cap per-call / per-session amounts.

Notes

Mirrors the official x402 MCP client pattern: https://docs.x402.org/guides/mcp-server-with-x402 . The x402 v2 TypeScript packages (@x402/axios, @x402/evm) evolve quickly — if npm install or the build fails, check that guide for current package names/versions.

No accounts, no API keys on the service side. Educational signals — not financial advice. MIT licensed.

Source: mcp/README.md at commit eb29762

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signals integrations