jquants-mcp@1.6.0
VERIFIED· not startedPublisher claims: "MCP server for retrieving Japanese stock market data via J-Quants API v2" 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
FIRESTORE_TOKEN_STOREJQUANTS_API_KEYJQUANTS_TOKEN_FILEMCP_STDIO_SERVE_TOKENMCP_STDIO_SERVE_TOKEN_FILEor--auth-token/--enable-oauth/--access-token-ttl/--oauthConfiguration, not credentials: GCS_BUCKET, GCS_PREFIX, GCS_SYNC_INTERVAL, GOOGLE_CLOUD_PROJECT, JQUANTS_API_TOML_PATH, JQUANTS_CACHE_DIR, JQUANTS_CLOUD_RUN_SERVICE, JQUANTS_CLOUD_RUN_URL, JQUANTS_MCP_USER, JQUANTS_PLAN, K_SERVICE, NEW_KEY, OLD_KEY- Where it talks to
- jquants.com, jpx-jquants.com (its own)Also aikawa.jp, claude.ai, meta.ai, run.app — 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 with a scoped credential, under the guard, and read the third-party hosts first. The code names aikawa.jp, claude.ai, meta.ai, run.app as well as its own vendor. The guard injects FIRESTORE_TOKEN_STORE, JQUANTS_API_KEY, JQUANTS_TOKEN_FILE, MCP_STDIO_SERVE_TOKEN, MCP_STDIO_SERVE_TOKEN_FILE only into requests to jquants.com (and its subdomains) and refuses the rest.
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-14 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
main .db file will be missing recent changes when uploaded to GCS.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.# echo 'JQUANTS_API_KEY=xxx' > .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.r = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…orical data bulk fetch via J-Quants Bulk API - `gcs_sync.py` — Cloud Run cache.db startup download from GCS (`--init-cache`). Skips the download (and the atomic replace that always allocates a new inode, which would invalidate `CacheStore`…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…hika/jquants-mcp/compare/v0.48.0...v0.48.1) (2026-06-09) ### Documentation * update Cloud Run sizing in CLAUDE.md to 2 vCPU + 8Gi ([#471](https://github.com/shigechika/jquants-mcp/issues/471)) …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.kill -TERM "${SERVE_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.&& chown -R appuser:appuser /app /home/appuserFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.&& chmod +x /usr/local/bin/supercronic \Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.kill -TERM "${GCS_DAEMON_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill -TERM "${GCS_DAEMON_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill -TERM "${SUPERCRONIC_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill -TERM "${SERVE_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# `docker compose` reads .env automatically, and .env is gitignored. PassingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.r = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.RUN chmod +x /app/scripts/entrypoint-compose.sh /app/scripts/entrypoint-stdio.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# 4. Start background GCS sync daemon (users.db + oauth_state.db upload only)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.kill -TERM "${SUPERCRONIC_PID}" 2>/dev/null || trueFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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
No advisories in OSV for jquants-mcp@1.6.0 as of 4 h ago. This is the package itself, not its dependencies.