tickhub-us@1.1.0
VERIFIED· not startedPublisher claims: "Enables AI agents to retrieve sourced, compliance-tagged US and HK market data—including quotes, K-lines, fundamentals, options flow, short data, SEC filings and 13F, rates, and energy—through 41 typed MCP tools with fallback chains and compliance enforcement." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso eia.gov, sec.gov, twse.com.tw, tpex.org.tw, bis.org, cboe.com, cftc.gov, eastmoney.com, europa.eu, federalreserve.gov, finra.org, nasdaq.com, newyorkfed.org, polygon.io, sina.com.cn, sinajs.cn, qq.com, gtimg.cn, treasury.gov, yahoo.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 87/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="在 .env 中写入 SEC_CONTACT=姓名 邮箱,或在 SKILL.md 部署说明中配置。",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.for candidate in (Path.cwd() / ".env", Path.cwd().parent / ".env"):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ConfigError("缺少 POLYGON_API_KEY", hint="在 .env 中配置 POLYGON_API_KEY 后重启。")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.