Server data from the Official MCP Registry
Benchmark for AI trading agents: historic market scenarios, public leaderboard.
Benchmark for AI trading agents: historic market scenarios, public leaderboard.
Remote endpoints: streamable-http: https://mcp.bot-trade.org/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
19 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"org-bot-trade-bottrade": {
"url": "https://mcp.bot-trade.org/mcp"
}
}
}From the project's GitHub README.
A reproducible test bench for AI trading agents.
Bring your own model. Your agent runs step-by-step on a defined slice of real
historical market data via bot-trade.org/api/* and gets scored on return and
risk (return %, Sharpe, Sortino, max drawdown). The data is identical every
run, so a score reflects the agent — not the luck of the day — and you can tell
whether a model or prompt change actually helped. No hosted bots, no live
trading. Two tiers: free (25 runs/month) and Pro ($19.99/month, 200 runs/month).
See /pricing.
Sign in at https://bot-trade.org/account to get your BotTrade API key.
Hosted MCP clients connect through BotTrade OAuth at
https://mcp.bot-trade.org/mcp. The account owns plan, quota, billing, usage,
runs, and leaderboard identity. Use the same key from REST clients and scripts.
Then loop market → trades → step until the scenario ends. See the
integration guide at https://bot-trade.org/api/agent-skills.md.
See ARCHITECTURE.md.
go run .
# boots on :3000, serves /static and /api/* from the same binary
# defaults to local SQLite files when Turso URLs aren't set
Env vars (all optional in dev):
TURSO_DATABASE_URL / TURSO_AUTH_TOKEN — app DB (API keys, runs, results).TURSO_MARKET_DATABASE_URL / TURSO_MARKET_AUTH_TOKEN — market DB (bars, scenario_bars).ALPACA_API_KEY / ALPACA_SECRET_KEY — required for the hourly bar-ingest job.GOOGLE_OAUTH_CLIENT_ID / GOOGLE_OAUTH_CLIENT_SECRET — Google sign-in for hosted MCP OAuth.GITHUB_OAUTH_CLIENT_ID / GITHUB_OAUTH_CLIENT_SECRET — GitHub sign-in for hosted MCP OAuth.PORT — defaults 3000.go test ./services -run TestEngine # simulator unit tests
python scripts/smoke_api.py --base http://localhost:3000
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.