Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AKQuant

PYPI · AKQUANT

Write and backtest trading strategies with AKQuant: API lookup, strategy checks, backtest runs

Available components

+18 this week 83 Trust /100

Last scanned (13 hours ago)

Scores higher than 83% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs maturin at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to akfamily/akquant). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1031 tokens (~147/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.3.94 → 0.3.95 functional
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.92 → 0.3.94 functional
    • Package version: 0.3.92 → 0.3.93 functional
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.91 → 0.3.92 functional
  • 16 Nov 26 +16
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.30 → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.90 → 0.3.91 functional
  • 15 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Schema quality: 129 → 151 ▼ functional
    • Package version: 0.3.89 → 0.3.90 functional
  • 14 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.88 → 0.3.89 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/akquant@0.3.95

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo akfamily/akquant
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/akfamily/akquant/.github/workflows/release.yml@refs/tags/v0.3.95
Rekor log index 4031985521
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:def2f63efa97143ab93d6a7c3ef0bdd80be350a044e607e8d200172599a3b8bd

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool maturin

Background: Why install scripts are a supply-chain risk →

Dependencies 17 packages
Packages resolved 17
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~850 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_strategy ~117

静态检查策略文件(不执行代码). path 相对项目根目录。返回 ok、类信息与 diagnostics(语法错误、 找不到/多个 Strategy 子类、拼错的 self 方法、Strategy 方法的错误 关键字参数或实参个数、回调入参上不存在的属性(如 bar.clsoe)、 on_bar 里的 self.I 等)。文件有多个 Strategy 子类时用 strategy_attr 指定类名。

NameTypeReqDescription
pathstringyes–
strategy_attr–––

Structured output declared, but exposes no named fields.

No examples provided.

get_api ~67

返回一个 API 的完整签名与 docstring. name 例: run_backtest、Strategy.buy、Strategy.I、 run_backtest.initial_cash、Bar.close、BarBatch.missing。找不到时 错误信息里给出相近名称。

NameTypeReqDescription
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_guide ~57

读取写策略要点. 不传 topic 返回主题列表; 传 topic(如 strategy-skeleton、indicators) 返回该篇 Markdown 全文。写新策略前先读 strategy-skeleton。

NameTypeReqDescription
topic–––

Structured output declared, but exposes no named fields.

No examples provided.

get_run_details ~61

分页读取一次回测的成交、委托(含拒单原因)、日频权益或日志.

NameTypeReqDescription
limitinteger––
offsetinteger––
run_idstringyes–
sectionstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

prepare_data ~198

准备回测数据并缓存, 返回 dataset_id 与摘要(含 issues). spec.source 二选一: file: {"source": "file", "path": "data/x.csv", "symbol"?, "timezone"?}, path 须在项目根目录或 AKTools 数据目录内。读 AKTools save_data 存下的 文件时, path 填它返回的路径并必须传 symbol(如 "600519"); 取数时优先 选新浪财经、腾讯的接口(成交量单位是股; 东方财富行情接口的中文列名 也认, 但成交量单位是手, 不做换算); synthetic: {"source": "synthetic", "symbols"?, "start"?, "end"?, "freq"?: "1d"|"1m", "seed"?}(只用于验证能跑通)。

NameTypeReqDescription
specobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

run_backtest ~240

在子进程中回测策略文件, 返回 status(ok/error/timeout)与摘要. config 只接受: initial_cash, commission_rate, stamp_tax_rate, min_commission, slippage, t_plus_one, lot_size, timezone, symbols, start_time, end_time, broker_profile, warmup_period。 slippage 必须是字典, 如 {"type": "percent", "value": 0.0002}; {"type": "zero"} 表示关闭滑点(含覆盖 broker_profile 模板的滑点)。 strategy_params 只能传类体里 IntParam 等声明过的参数。失败时看 error.phase、error.user_frames(策略文件里的行号; 指标声明引起、在 框架里抛出的错误指回 self.I 声明行)与 error.hint。 每次调用都重新加载文件, 改完直接重跑即可。

NameTypeReqDescription
config–––
dataset_idstringyes–
pathstringyes–
strategy_attr–––
strategy_params–––
timeout_sinteger––

Structured output declared, but exposes no named fields.

No examples provided.

search_api ~110

按关键词搜索 AKQuant 公开 API. 范围: akquant 顶层导出、Strategy 的方法与属性、run_backtest 的参数 (名称形如 run_backtest.initial_cash)、其余导出类的成员(名称形如 Bar.close、BarBatch.missing)。名称命中排在 docstring 命中之前。 返回名称、类型与一句摘要; 详情用 get_api。

NameTypeReqDescription
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the AKQuant MCP server?

AKQuant runs locally as a PyPI package, launched with uvx --with 'akquant[mcp]==0.3.95' akquant mcp, plus the required --root, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

pypi · akquant

# add to Claude Code
claude mcp add akfamily-akquant -- uvx --with 'akquant[mcp]==0.3.95' akquant mcp

Incomplete: the registry marks --root as required and gives no value we can show, so it is not in this command. Add it before you run it.

Common questions

What is the AKQuant MCP server?

AKQuant is an MCP server listed in the public MCP registry as io.github.akfamily/akquant. Write and backtest trading strategies with AKQuant: API lookup, strategy checks, backtest runs. This page covers its PyPI package (akquant).

Is the AKQuant MCP server safe to use?

AKQuant scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AKQuant MCP server expose?

AKQuant exposes 7 tools: search_api, get_api, get_guide, check_strategy, prepare_data, and 2 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.

Is the AKQuant MCP server still maintained?

AKQuant is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AKQuant MCP server under?

AKQuant declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the AKQuant MCP server?

VerifyMCP ran 16 checks on AKQuant, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.