Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add shigechika/jquants-mcpnpx agentmods add plugins/shigechika/jquants-mcp/plugingit clone --depth 1 https://github.com/shigechika/jquants-mcpGrade A, and why
jquants-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "jquants-mcp",
"displayName": "J-Quants MCP",
"description": "Japanese stock market data via J-Quants API v2, for Claude Code. 55 tools covering equities, financials, indices, derivatives, margin/short-selling data, market-wide screeners, technical indicators, and JSON chart data, backed by a local SQLite cache. Zero-config on a machine that already runs jquants-api-client (auto-reads ~/.jquants-api/jquants-api.toml); otherwise run `jquants-mcp login` or set JQUANTS_API_KEY.",
"author": {
"name": "AIKAWA Shigechika",
"url": "https://github.com/shigechika"
},
"homepage": "https://shigechika.github.io/jquants-mcp/",
"repository": "https://github.com/shigechika/jquants-mcp",
"license": "MIT",
"keywords": [
"jquants",
"stocks",
"japan",
"market-data",
"finance",
"trading",
"screener"
]
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 23 lines scan A ce3151653abb
jquants-mcp is a plugin published in the GitHub repository shigechika/jquants-mcp (2 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
unraid-mcp
Marketplace for the Unraid MCP plugin — query, monitor, and manage Unraid servers from Claude Code.
rival-search-mcp
9 research tools: 5-engine web search, 9 social platforms, 5 news sources, 5 academic databases, GitHub, website mapping, document analysis, and research topic synthesis. No API keys required. Deterministic outputs for agent chaining.
zulipchat
Connect Claude Code sessions to Zulip topics with lifecycle hooks, owner approvals, and bidirectional control.
servicenow
ServiceNow admin toolkit — incidents, CMDB, update sets, table explorer. 19 MCP tools + 4 guided skills.
apollo-mcp
FastMCP server exposing the full operational surface of the Apollo.io REST API. 27 tools covering sequences, campaign health, mailbox warmup, people/org enrichment, CRM contacts, tasks, labels, credit tracking, and programmatic template/sequence/mailbox-cap editing with audit logging.
slack-mcp
Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, and triple-mode auth (xoxc/xoxp/xoxb).