ticktest-mcp@0.4.1
VERIFIED· install onlyPublisher claims: "TickTest A股量化回测 MCP Server — 让 AI Agent 用自然语言回测 A 股" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 2 of 2 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
TICKTEST_API_KEYConfiguration, not credentials: TICKTEST_API_URL, TICKTEST_BACKTEST_TIMEOUT- Where it talks to
- ticktest.cn (its own)
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for TICKTEST_API_KEY and talks to ticktest.cn. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"hint": "请在 mcpServers 配置的 env 中更新 TICKTEST_API_KEY。获取新 Key: https://ticktest.cn/keys",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."hint": "请在 mcpServers 配置的 env 中更新 TICKTEST_API_KEY。获取新 Key: https://ticktest.cn/keys",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."hint": "在 mcpServers 配置的 env 中添加 TICKTEST_API_KEY。注册地址: https://ticktest.cn",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them."hint": "请在 mcpServers 配置的 env 中更新 TICKTEST_API_KEY。获取新 Key: https://ticktest.cn/keys",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for ticktest-mcp@0.4.1 as of 6 h ago. This is the package itself, not its dependencies.