oneconnecter-plugin vs J-Quants MCP
oneconnecter-plugin is a plugin bundle for AI coding tools published by techne-labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). J-Quants MCP is an MCP server published by shigechika. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  oneconnecter-plugin |  J-Quants MCP |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.1 Downloads/month (PyPI): 517 Downloads/week (PyPI): 437 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | oneconnecter-plugin | J-Quants MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (api.oneconnecter.io/mcp) | On your machine (jquants-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/techne-labs/oneconnecter-plugin | github.com/shigechika/jquants-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
oneconnecter-plugin
Real-time data for AI agents through intelligent semantic routing. Access weather, cryptocurrency prices, stock market data, commodities, and company intelligence. Instead of overwhelming Claude with dozens of tools, OneConnecter routes queries to specialized data agents - right source, every time. Features semantic caching (78% token reduction), sub-second routing, and multi-intent query splitting. Perfect for financial research, market monitoring, and any workflow needing live external data.
J-Quants MCP
MCP server for retrieving Japanese stock market data via J-Quants API v2
How to run each
oneconnecter-plugin As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install oneconnecter-plugin@claude-communityJ-Quants MCP As a local MCP server: PyPI package
claude mcp add --transport stdio jquants-mcp -- uvx jquants-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only oneconnecter-plugin has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: oneconnecter-plugin · What it can do: J-Quants MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.