tick-stock-panel: A self-hosted quantitative workbench for building A-share strategies, monitoring markets, and researching backtests.
What problem it solves
Quant research often fragments data collection, strategy development, backtesting, and monitoring across separate tools, causing inconsistent data definitions and duplicated integration work. TSP provides a unified, self-hosted workspace that keeps data local while exposing its capabilities through interfaces for custom tools and AI clients.
Key features
Open APIs and MCP integration — Core capabilities are exposed through permissioned API endpoints, an SSE event stream, and MCP tools so external programs and AI clients can consume the same functions as the panel.
Source: README, mcp-server
Local-first deployment and extension — A single-container deployment uses local file-based storage without an external database. Data sources, strategies, signals, pages, and backend modules can be added or removed through extension channels.
Source: README, Dockerfile
Quick start
Copied verbatim from the project's README.
# 十行内跑通第一个调用
curl -H "Authorization: Bearer tsp_xxxx" \
"http://localhost:3018/api/kline/daily?symbol=600519.SH&limit=10"Who it may suit
This project may suit A-share quantitative researchers and developers who want to combine strategy research, backtesting, monitoring, and local data management in one workspace. It may also suit teams building custom pages, scripts, bots, or AI-client integrations against a self-hosted deployment.
Topics to discuss
Which strategy and factor research workflow should the community prioritize next?
How should external data-source plugins define and preserve enriched data semantics?
Which open API or MCP workflows would be most useful for custom tools and AI clients?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/shy3130/tick-stock-panel#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…