How do I install Kraken Signals?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Kraken Signals need an API key?

The publisher lists these environment variables: EVM_PRIVATE_KEY, RESOURCE_SERVER_URL.

What transport does Kraken Signals use?

Kraken Signals runs locally over stdio.

Kraken Signals

Q: When was Kraken Signals last checked?

Last checked 2026-10-16. Kraken crypto signals via x402: free preview + paid USDC-on-Base signals, regime & indicators

by io.github.Nikoble1926

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y [email protected]

Credentials from the publisher

EVM_PRIVATE_KEY — Optional. 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_URL — Optional. Override the signals API base URL. Defaults to https://signals.nsgoods.org.

Provider

Claude Code

EVM_PRIVATE_KEY=<secret> RESOURCE_SERVER_URL=<value> claude mcp add io.github.nikoble1926-kraken-signals-mcp -- npx -y [email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.nikoble1926-kraken-signals-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "<secret>",
        "RESOURCE_SERVER_URL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

kraken-crypto-signals

Pay per call crypto market state and regime signals for AI agents, served over the x402 protocol. Every response is a signed, verifiable verdict.

What this is (for AI agents): a pay per call HTTP 402 endpoint that returns signed, machine readable crypto market state. No accounts, no API keys. Pay USDC on Base, get data you can verify yourself.

What it does

Market state signals and technical indicators, returned on demand per call over HTTP 402
Built for autonomous agents that need a signed read of current conditions
Free preview endpoints so you can see the shape before you pay

How it works

Signed with EIP-191; every verdict is canonicalized and independently verifiable
Settled per call in USDC on Base
You pay only for a successful 2xx response

Live: signals.nsgoods.org Manifest: /.well-known/x402 · OpenAPI: /openapi.json

Part of nsgoods, a suite of signed x402 data oracles. Hub: x402.nsgoods.org