Analytics
alktrading.com
Provides live trading signals, closed track records, historical backtest scores, and plain-English strategy rules from the ALK trading board.
ENDPOINT 1
https://alktrading.com/mcp
MCP server metadata
- Name
- alktrading
- Version
- 1.0.0
Read-only ALK Trading data: live signals, the published track record, stored backtest scores and strategy rules. Every answer links to its alktrading.com source. Educational only, not financial advice.
Known tools 6
get_backtestStored historical backtest scores for one ticker (as shown on alktrading.
Inferred read-onlylist_strategiesThe public rule set ALK signals are built from: id, name, badge and a one-line summary.
Inferred read-onlyexplain_strategyPlain-English rules for one ALK strategy: the rule, long trigger, short trigger and the market it suits.
Inferred read-onlyCONNECT 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.alktrading]
url = "https://alktrading.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"alktrading": {
"type": "http",
"url": "https://alktrading.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: alktrading
Remote MCP URL: https://alktrading.com/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": {
"alktrading": {
"url": "https://alktrading.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"alktrading": {
"type": "http",
"url": "https://alktrading.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "alktrading",
"transport": "streamable-http",
"url": "https://alktrading.com/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.