API Tools

x70.ai

An MCP server that accesses a crypto trading signals API to fetch live and historical signals, signal details with live PnL, and aggregated performance statistics.

1 endpoint5 known toolsFirst detected September 15, 2026Last detected September 15, 2026

ENDPOINT 1

https://signals.x70.ai/mcp

No auth detected

MCP server metadata

Name: trading-signals
Version: 1.0.0

Capabilities

tools.listChanged

Known tools 5

register

Create an API key to access trading signals.

Potential side effects

get_signals

Fetch live (active) crypto trading signals with entry, SL, TP, leverage, confidence.

Inferred read-only

get_signal

Fetch a single signal by ID with live price and PnL.

Inferred read-only

get_stats

Get aggregated performance: hit rate, average ROI per signal, average leverage, breakdown by direction.

Inferred read-only

get_signal_history

Fetch historical (verified) signals with pagination.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.trading-signals]
url = "https://signals.x70.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "trading-signals": {
      "type": "http",
      "url": "https://signals.x70.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: trading-signals
Remote MCP URL: https://signals.x70.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "trading-signals": {
      "url": "https://signals.x70.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "trading-signals": {
      "type": "http",
      "url": "https://signals.x70.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "trading-signals",
  "transport": "streamable-http",
  "url": "https://signals.x70.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.