A
licenseA
qualityD
maintenanceEnables AI clients like Claude Desktop to search J-Quants API endpoints, get detailed information, reference implementation patterns, and access FAQ answers using MCP.
7
6 npm
MIT
j-quants-doc-mcp
Officialby J-Quants
Related Servers
Alternatives to j-quants-doc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables access to the CSMAR financial database via MCP, providing tools for querying financial data, stock data, company info, and more through natural language in compatible clients like Codex and Claude Code.6 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables programmers to search, download, and access up-to-date API and software documentation through MCP tools, integrating with LLMs like Claude for Desktop.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and fetching Claude and Anthropic documentation with intelligent relevance scoring, optimized for MCP development, APIs, and examples.10 npm6MIT
- AlicenseBqualityDmaintenanceEnables AI-driven semantic code search via natural language queries, integrating with MCP clients like Claude Desktop to retrieve relevant code context from any codebase.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to search Groq's API documentation using natural language queries through an MCP-compatible interface.MIT
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: health check, endpoint search, endpoint details, pattern lookup, spec page fetch, migration guide, and FAQ/info routing. No two tools overlap in functionality; the boundaries are explicit and well-documented.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (health_check, search_endpoints, describe_endpoint, get_pattern, fetch_spec_page, migrate_v1_to_v2, get_info). The only minor deviation is 'health_check' being a noun phrase rather than verb_noun, but all are snake_case and clear.
Tool Count5/5
7 tools is well within the ideal 3-15 range and each covers a distinct aspect of an API documentation MCP server: health, search, detail, patterns, page fetching, migration, and general info. The scope is appropriately sized with no redundant tools.
Completeness4/5
The tool surface covers the core needs of exploring an API spec: search, describe, fetch arbitrary pages, and migration guidance. Minor gaps like direct version comparison or credential handling are not necessary since the domain is documentation access, and get_info covers out-of-scope questions.
Maintenance
ActivityInactive
ResponsivenessUnresponsive