jquants-mcp (shigechika/jquants-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
69/100
23 days ago

jquants-mcp

An MCP server that retrieves Japanese stock market data via J-Quants API v2.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

shigechika

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: JQUANTS_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGCS_BUCKETset-env-vars "=YOUR_BUCKET,JQUANTS_CACHE_DIR=/tmp" \
configGCS_PREFIXNo jquants-mcp/ Object key prefix in the bucket
configJQUANTS_CACHE_DIRNo ~/.cache/jquants-mcp Cache directory path
configPUBSUB_INVOKER_SANo — Service account email for Pub/Sub push authentication. When set, /internal/reload verifies the Google-signed OIDC token. Required if using Pub/Sub auto-reload; leave unset otherwise.
configPUBSUB_AUDIENCENo request URL OIDC audience to verify against (defaults to the incoming request URL)
configK_SERVICE
configGOOGLE_CLOUD_PROJECTYes — GCP project ID. Required for Firestore (user DB) and Secret Manager access. Set via vars.GCP_PROJECT in the CD workflow
configJQUANTS_CLOUD_RUN_SERVICE
configJQUANTS_PLANNo auto-detect Plan: free / light / standard / premium (auto-detected from the API key at server startup; set this variable only to override)
configGCS_SYNC_INTERVAL
🔐 secretJQUANTS_API_KEYNo — J-Quants API key
configJQUANTS_ENV
configXDG_CONFIG_HOME
configJQUANTS_API_TOML_PATHNo ~/.jquants-api/jquants-api.toml Path to the J-Quants official config file. Override to avoid macOS 26+ launchd sandbox restrictions (see [macOS launchd note](#macos-launchd-note) below)
configXDG_CACHE_HOME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

55/55 tools missing one or more hints — health_check (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cache_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); cache_clear (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +52 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

52/55 tool handlers declare input schemas (95%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

33/55 tool handlers wrap calls in try/catch (60%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/shigechika-jquants-mcp-1yytch)](https://m8ven.ai/mcp/shigechika-jquants-mcp-1yytch)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e7de6f9d3033890318d28fbe76d9b62ac3a4b0d1
code hash: 0f471432095143cc682c502add8c132c6a4266bf7fb33afcf1e20430529a4381
verified: 8/7/2026, 2:40:35 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client