tickdb-unified-realtime-marketdata-api
TickDB: AI-native real time stock API and market data API for US/HK/CN stocks, forex, futures, crypto, indices and commodities. Skill, CLI, MCP, REST API and WebSocket. AI 原生实时股票 API 与金融行情数据 API,覆盖美股、港股、A股、外汇、期货、指数、大宗商品、加密货币。
Runssource: GitHubhomepagePythonMITcommit 37b2d3c13034
Python, MIT licensed. The project labels itself: ai agents, cli tool, commodities, financial analysis, financial data, forex, futures and indices.
tickdb-unified-realtime-marketdata-api runs. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
TickDB MCP server installs from source, all 49 unit tests pass, server starts on port 8000 with 13 MCP tools registered and responds correctly to MCP Streamable HTTP requests.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- mcp package resolved to v2.3.0 which broke FastMCP import1 minute
- externally-managed-environment blocked pip install
- Install time
- 2 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pytest tests/ -v ran 49 passed; server started in HTTP mode returned 200 on POST /mcp with initialize; tools/list returned 13 tools via SSE; examples/server_demo.py completed all steps
- Model tokens used
- 176,053
- Exact commit tested
- 37b2d3c13034
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
| `mcp` resolved to v2.3.0 which renamed FastMCP to MCPServer | Pinned `mcp[cli]>=1.9.0,<2.0.0` in … **All 49 unit tests pass.** The MCP server boots on HTTP, responds with `200 OK` to valid MCP initi… tokens used 176,053 Everything is working. Let me compile the final report. ## Summary **Initial errors and fixes:** | Error | Fix | Time | |-------|-----|------| | Externally-managed Python environment blocked pip | Created a venv via `python3 -m venv .venv` | … | `mcp` resolved to v2.3.0 which renamed FastMCP to MCPServer | Pinned `mcp[cli]>=1.9.0,<2.0.0` in … **All 49 unit tests pass.** The MCP server boots on HTTP, responds with `200 OK` to valid MCP initi…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes, faster than the median of the 26 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 27 ai-tools projects Argusic has installed and timed, tickdb-unified-realtime-marketdata-api was the 8th fastest to reach a running state, and 19 of 27 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.03 |
Topics (from GitHub)
ai-agentscli-toolcommoditiesfinancial-analysisfinancial-dataforexfuturesindicesmarket-datamcporder-bookreal-timerest-apiskillstock-apistock-datastock-marketstockstick-datawebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tickdb-unified-realtime-marketdata-api)Questions
- Does tickdb-unified-realtime-marketdata-api run?
- Yes. tickdb-unified-realtime-marketdata-api runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test tickdb-unified-realtime-marketdata-api?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 37b2d3c13034. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tickdb-unified-realtime-marketdata-api?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tickdb-unified-realtime-marketdata-api take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does tickdb-unified-realtime-marketdata-api need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tickdb-unified-realtime-marketdata-api?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tickdb-unified-realtime-marketdata-api compare with the alternatives?
- Of the 27 ai-tools projects Argusic has installed and timed, tickdb-unified-realtime-marketdata-api was the 8th fastest to reach a running state, and 19 of 27 reached one at all.
- Where is the evidence for tickdb-unified-realtime-marketdata-api?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.