MCP servers › io.github.akfamily › akquant
MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18
akquant MCP server
Registry name io.github.akfamily/akquant
by akfamily · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗Website ↗
Write and backtest trading strategies with AKQuant: API lookup, strategy checks, backtest runs — the publisher's description
Summary
io.github.akfamily/akquant is a local MCP server listed in the official MCP registry at version 0.3.92, under the namespace of the GitHub account akfamily. Its linked repository, github.com/akfamily/akquant, belongs to the same GitHub account.
Record checks
8 of 8 record checks met · 1 does not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #212 of 20,610 packages by monthly downloads
- #146 of 28,859 repositories by GitHub stars
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- PyPI · listed version current
- License
- MIT License
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.3.92, published 2026-11-17 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 14 versions listed, 2026-11-06 to 2026-11-17; 14 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 12 versions
0.3.92· 2026-11-170.3.91· 2026-11-160.3.90· 2026-11-150.3.89· 2026-11-140.3.88· 2026-11-130.3.87· 2026-11-120.3.86· 2026-11-120.3.85· 2026-11-110.3.84· 2026-11-090.3.83· 2026-11-080.3.82· 2026-11-070.3.81· 2026-11-07
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.3.91 (published 2026-11-16) → 0.3.92 (published 2026-11-17), between the registry lists of 2026-11-17 and 2026-11-18.
The publisher’s GitHub release note for v0.3.92, published 2026-11-17.
Read the release note (the publisher’s text, shown as plain text)
> 规则版本 2.4.1 → 2.4.2:量限改为整根 bar 共用、FOK/IOC 按语义终结,保证金账户的账户级风控改用账户口径权益并放行减仓单,最低佣金改为按委托收,按金额设的风控限额计入合约乘数(见下文)。只有“保证金账户 + 期货 + 账户级风控”“账户级风控触发后下减仓单”“开了量限且同一根 bar 上同一标的有多笔委托”“开了量限且用了 IOC/FOK”“量限把小额委托拆成多笔成交”“期货/期权上设了按金额的限额”这几类回测结果会变,其余不变。 ### Fixed - **walk-forward 把预热段的盈亏算进了样本外**:`run_walk_forward` 的每段样本外回测从“样本外起点前 `warmup_period` 根”开始跑,预热期内不调 `on_bar`,但 `on_after_trading`、`on_timer` 等回调照常触发;策略在这些回调里下单时预热段就有成交,而每段样本外的收益此前一律以 `initial_cash` 为基准,这部分盈亏被计入了样本外净值。现在以样本外起点前最后一个权益点为基准。只在 `on_bar` 里下单的策略预热段没有成交,结果不变。 - **量限按整根 bar 共用,不再对每笔委托各算一次**:`volume_limit_pct` 此前对每笔委托单独按“成交量 × 比例”截断,同一根 bar 上 8 笔各 2500 股的委托(成交量 10000、比例 0.25)合计能成交 20000 股,是整根成交量的 2 倍——拆单、多策略槽位、同一标的多笔挂单都会突破量限。现在同一根 bar 上该品种的全部委托共用一个上限,按撮合顺序(先卖后买,同方向按提交先后)依次扣减,用完后其余委托留到后续 bar。只有一笔委托时结果不变。tick 驱动的撮合仍不受量限约束。 - **FOK 会部分成交、IOC 剩余量不撤销**:开了量限后,被截断的 `FOK` 委托会先成交一部分,`IOC` 委托的剩余量继续挂着、之后的 bar 接着成交,二者与普通委托没有区别(0.3.74 记录的已知问题)。现在 `FOK` 当根成交不完就一股不成交、整笔撤销;`IOC` 成交当根能成交的部分,剩余量随即撤销,订单终态为 `Cancelled` 且 `filled_quantity` 为已成交量,`on_order` 收到的也是这个终态。带 OCO 或括号单的 `IOC` 委托按成交处理:对手单照常撤销,止盈止损按已成交量挂出。 - **部分成交后当步被撤的委托,`on_order` 终态被报成已成交**:一笔委托在同一步里既有成交又被撤销时,策略回调收到的终态是 `Filled` 且成交量为旧值。现在以引擎里的终态为准(`Cancelled`,带实际成交量)。 - **保证金账户里账户级风控按错误的权益判定**:`max_account_drawdown`、`max_daily_loss`、`stop_loss_threshold`、`max_position_pct`、总杠杆和行业集中度六条规则,以及 `buying_power`、提交委托时的资金校验,此前把“现金 + 持仓名义市值”当权益。保证金账户(`account_mode="margin"`)开期货仓只占保证金、不扣名义额,于是:持多头时名义额被加进权益,真实亏损 30% 也触发不了回撤规则;持空头时开仓瞬间就被判成亏损;多头平仓后“权益”回落被当成回撤,之后的新单全部被拒。现在统一用账户口径的权益(期货持仓只计浮动盈亏),与 `get_account()["equity"]` 一致。现金账户不受影响。 - **账户级风控触发后连减仓单一起拒**:上述六条规则触发后此前不分开仓减仓一律拒单,仓位平不掉。现在只拒会增加风险的委托,方向与持仓相反且数量不超过持仓的减仓单放行;超过持仓的反手单,平仓腿放行、开仓腿被拒。 - **最低佣金按委托收,不再按成交收**:开了量限(`volume_limit_pct`,A 股标准模板默认开)后,一笔委托会被拆成多笔成交,此前每笔成交各收一次最低佣金——买 300 股拆成 3 笔,佣金从 5 元变成 15 元。现在整笔委托的佣金是“各笔成交佣金之和”与最低佣金中的较大者:首笔成交先按最低佣金收齐,之后的成交只补差额。一次成交完的委托不受影响;印花税、过户费仍按每笔成交额计。适用于股票、基金与 `SimpleMarket`。 - **按金额设的风控限额在期货、期权上漏乘合约乘数**:`strategy_max_order_value`、`strategy_max_daily_loss`、`strategy_max_drawdown`、`strategy_risk_budget`、`portfolio_risk_budget` 与账户级 `max_order_value` 此前一律按“价格 × 数量”计,螺纹钢(乘数 10)一手 4000 元的委托被当成 4000 元而不是 40000 元,浮亏 1000 元被当成 100 元,限额等于被放宽了“乘数”倍。现在都按“价格 × 数量 × 合约乘数”计。股票乘数为 1,不受影响。实盘 `broker_live` 的报单前校验同步修正;`akquant.check_strategy_limits` 新增可选参数 `multiplier`(不传按 1)。 - **回测里 `cancel_group` 撤不掉 OCO 组**:把 `place_oco` 返回的组号传给 `cancel_group` 时,回测会把组号当成订单号去撤,引擎找不到这个号,只留一条日志,两笔订单都还挂着,也不报错。现在按组号撤掉组内全部订单;传拆腿的下单回执时每条腿都撤。实盘不受影响。 - **Rust 侧崩溃时实盘收尾摘要写成“Manual Stop”**:引擎内部 panic 抛出的异常不属于 `Exception`,此前绕过了错误处理,摘要标题仍是 `Manual Stop`,也没有 CRITICAL 日志,崩溃的会话看起来像正常手动停止。现在摘要标为 `ABORTED ON ERROR` 并记 CRITICAL,异常照旧向外抛;`on_stop` 与此前一样会执行。 - **教材第 15 章把回测存档写成了实盘恢复手段**:“回测→实盘最小切换清单”曾建议用 `save_checkpoint` / `run_from_checkpoint` 实现宕机后续跑,但这两个接口只用于回测与历史回放,`run_live` 不读也不写存档。已改为实际情况,并在 15.5.4 补充说明:实盘重启后持仓、资金、柜台挂单从柜台重新同步,本地止损单、OCO/括号单关系和策略变量会丢失,需要策略自行重建。 - **回测入口的类型存根漏了 tick 输入**:`run_backtest(data=...)` 一直接受 `list[Tick]` 与 `Bar`、`Tick` 混合的列表,但类型存根里的 `BacktestDataInput` 没有列出,传 tick 列表时类型检查器会误报。现已补上,运行行为不变。 - `docs/llms.txt`(给 AI 助手看的说明)仍写着 `prepare_data` 支持 `source="akshare"`、`akquant[mcp]` 自带 AKShare,已改为 0.3.91 的实际情况,并补上“AKTools `save_data` 存盘,再用 `source="file"` 读入”的两步用法。 ### Performance - **只有日期的日线回测提速约 2.5 倍**:单标的日线、空策略由每根 bar 约 60 微秒降到 22~30 微秒(1,456 根由 100 毫秒降到约 43 毫秒,20,000 根由 1.1 秒降到约 0.44 秒)。此前每个交易日各做一次带时区的 `pd.Timestamp` 换算(约 18 微秒一次),占这类回测耗时的六成;现改为整批换算,结果逐值不变。分钟线和 tick 回测本来不走这条路径,耗时基本不变。 ### Changed - **联网示例在取数失败时改用合成数据,不再直接报错退出**:`examples/` 下 11 个示例(`01_quickstart`、`11`、`17`、`21`、`26`、`59` 与 `strategies/01`~`04`、`06`)此前在未安装 AKShare、断网或 AKShare 接口改名时直接报错。现在会打印一行警告并改用固定种子的合成日线跑完;合成数据的回测结果没有参考意义。能取到数据时行为不变。 - `docs` 可选依赖里的 AKShare 下限由 1.0.0 提高到 1.20.64(示例与内置日历更新脚本用的是该版本起的接口名),并限定 Python 3.11 及以上才安装。 ### Internal - `scripts/bench_engine_perbar.py` 新增 `daily` 档位(单标的只有日期的日线、空策略),用来盯住每个交易日一次的 Python 侧日期换算开销;原有档位都是多标的或分钟线,这部分开销被摊薄后看不出来。 - CI 新增 `Tests` 工作流:在 PR 与 `main` 上跑全部 Python 测试(此前测试只在本地跑)。
Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
How do I add it to my client?
Config from the registry entry
- No config: the PyPI package declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.3.92
- Latest stable
- 0.3.92
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-11-18. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-18 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-571480cf9b2ac7bb5…
- License
- MIT License
Source: the package registry · 2026-11-18.
Usage
- Downloads
- 14,970 in the last month
Source: pypistats.org · 2026-11-18.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Python version and wheels (PyPI). Needs Python 3.10 or later (requires_python
>=3.10). Source: pypi.org/pypi/akquant/0.3.92/json · read 2026-11-18. - Build workflow. Built and published by GitHub Actions workflow
release.ymlinakfamily/akquant(PyPI provenance). Source: pypi.org/integrity/akquant/0.3.92/akquant-0.3.92-cp310-abi3-macosx_11_0_arm64.whl/provenance · read 2026-11-18.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-18.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://akquant.akfamily.xyz/.well-known/ (HTTP 404, 2026-11-18). Source: akquant.akfamily.xyz/.well-known/security.txt · read 2026-11-18.
- A2A agent card. No A2A agent card at https://akquant.akfamily.xyz/.well-known/ (HTTP 404, 2026-11-18). Source: akquant.akfamily.xyz/.well-known/agent-card.json · read 2026-11-18.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.3.92 on PyPI | Exists and can be installed | matches | PyPI · 2026-11-18 |
| Repository github.com/akfamily/akquant | Opens publicly | matches | api.github.com · 2026-11-18 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.akfamily · 2 servers
- GitHub owner
- an organization (akfamily)
- Repository
- github.com/akfamily/akquant
- Stars
- 2,616
- Repository age
- 181–365 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- owner's .github/SECURITY.md
Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-07.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating8 of 8 record checks met · 1 does not apply
- #212 of 20,610 packages by monthly downloads
- #146 of 28,859 repositories by GitHub stars
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierMIT License
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.akfamily/akquant
Answered from the data aboveWho publishes io.github.akfamily/akquant?
The registry ties the namespace io.github.akfamily to the GitHub account akfamily; only its owner can publish under it. Its linked repository, github.com/akfamily/akquant, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.akfamily/akquant safe to install?
We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.akfamily/akquant been security tested?
No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.
Does io.github.akfamily/akquant publish a security policy?
Yes: its repository has a public security policy (github.com/akfamily/.github/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.3.92, the latest stable release on PyPI.
Where is the source code of io.github.akfamily/akquant?
In github.com/akfamily/akquant, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.akfamily/akquant: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.akfamily/akquant
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.akfamily/akquant)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology