INDIVIDUAL MCP TOOL
get_signal
Get one signal by its ID — live or already resolved — with its reasoning, live price, PnL and verification outcome (status pending, success or failed; whether take-profit or stop-loss was hit).
LIVE ENDPOINT
https://signals.x70.ai/mcp
Connect to this endpoint to inspect the live schema for get_signal and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
register— Deprecated: returns a sign-up link instead of creating an API key, ignores its arguments and stores nothing.get_signals— List live crypto trading signals that are still open — coin, direction, confidence and the reasoning or market data behind each.get_stats— Aggregate performance of signals created in the last N days (default 30) that have since resolved: hit rate, verified count, average leverage and a breakdown by direction; with an API key also average ROI per signal and cumulative ROI.get_signal_history— List signals that have already resolved (success or failed), newest first, each with its verification outcome.