x4

x402 Dev Console

v1.0.0

← Back to MCP Servers
╔══╗
║TS║
║$$║
╚══╝

Real-Time Trading Signals

v2.1.0TradingTools 4 actions
Use with an LLMTry in Playground

SERVER URL

http://localhost:3000/api/mcp-server/trading-signals

CONNECTION JSON

{
  "mcpServers": {
    "trading-signals": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "http://localhost:3000/api/mcp-server/trading-signals"
      ]
    }
  }
}

Learn more about supported MCP clients

MCP HOST CONNECTIONS

Connect this MCP server directly to your AI assistant tools by using the JSON config above. Click on a logo to see a demo video.

╔═══╗
║ ▸ ║
║ │ ║
╚═══╝
CursorWatch demo
┌───┐
│ C │
│ L │
└───┘
ClaudeWatch demo
≋≋≋≋
~≋~≋
≋~≋~
~~~~
WindsurfWatch demo

DESCRIPTION

Real-time trading signals powered by AI and on-chain analysis. Pay per signal with x402 protocol. Get entries, exits, stop losses, and confidence scores for crypto and traditional markets.

AVAILABLE TOOLS

x402_subscription_status

Check active subscription or pay for access

get_crypto_signals

Get latest crypto trading signals (requires x402 payment)

get_stock_signals

Get stock market signals (requires x402 payment)

backtest_strategy

Backtest trading strategy (premium - requires x402 payment)

CODE EXAMPLES

JavaScript
// Trading Signals with x402
import { Client } from '@modelcontextprotocol/sdk';

const client = new Client();
await client.connect('https://signals.x402.app/mcp');

// Check subscription or get payment requirements
const status = await client.callTool({
  name: 'x402_subscription_status',
  arguments: { wallet: 'YourWallet...' }
});

// Get signals (auto-pays if needed)
const signals = await client.callTool({
  name: 'get_crypto_signals',
  arguments: {
    assets: ['SOL', 'BTC', 'ETH'],
    wallet: 'YourWallet...'
  }
});

Official MCP SDK Documentation:
https://github.com/modelcontextprotocol/modelcontextprotocol

Installation:
npm install @modelcontextprotocol/sdk

Authentication:
- For MCP Hosts (Cursor, Windsurf, Claude Desktop), saving the JSON config to your tool will automatically trigger the browser OAuth flow
- For programmatic access, obtain the OAuth token by running "npx mcp-remote <url>" in the terminal and follow the instructions

x4