mcpField
K
kraken-signals-mcp

kraken-signals-mcp

Local
github.com/Nikoble1926Finance1Updated 6w ago

About kraken-signals-mcp

kraken-signals-mcp exposes Kraken crypto-market signals and analysis through free preview and paid tools. It is for MCP clients that need pair-specific signals, market scans, historical snapshots, regime changes, backtests, or technical indicators.

Key features

  1. 01Free BTC/USD signal preview
  2. 02Pair signals and scans across major markets
  3. 03Historical snapshots with verifiable hashes
  4. 04Market regime and change detection
  5. 05Backtests and technical indicators

Use cases

  1. 01Preview the current BTC/USD direction
  2. 02Compare signals across major trading pairs
  3. 03Review historical signal snapshots and hashes
  4. 04Inspect market regimes, backtests, or pair indicators

MCP support

Provides signal and analysis tools to MCP clients. Paid tools use x402 to pay USDC on Base when a wallet key is configured; the free preview requires no wallet key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"nikoble1926-kraken-signals": {
"command": "npx",
"args": [
"-y",
"kraken-signals-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "<EVM_PRIVATE_KEY>",
"RESOURCE_SERVER_URL": "<RESOURCE_SERVER_URL>"
}
}
}
}
Run commandnpx -y kraken-signals-mcp
Environment variables to set
EVM_PRIVATE_KEYSecretOptional. Base wallet private key (0x...) for a low-balance hot wallet holding a little USDC. Required only for the paid tools; the free get_signal_preview tool works without it. Never use your main wallet.
RESOURCE_SERVER_URLOptional. Override the signals API base URL. Defaults to https://signals.nsgoods.org.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmkraken-signals-mcp1.1.1

Tools

7

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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:

{
  "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:

{
  "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)

cd mcp
npm install
npm run build
node 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.