jp-verify-mcp
Related Servers
Alternatives to jp-verify-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying the Japanese corporate registry from METI's gBizINFO for company profiles, government procurement, subsidies, patents, certifications, financials, and workplace disclosures using corporate numbers or names.264 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to look up verified investor relations page URLs and earnings release (kessan tanshin) URLs for 3,821 Japanese listed companies by securities code, company name, former or brand name, and to fetch selected company attributes. Also supports retrieving monthly change data, checking credit balance and expiry, and inspecting available field definitions.6275 npmMIT
- AlicenseNot gradedqualityCmaintenanceTorify gives AI agents the Japanese locale primitives that standard libraries lack — imperial era date conversion (wareki), qualified invoice number validation with NTA registry lookup, corporate number lookup (法人番号), postal code resolution, name romanization (Hepburn), and kanji-to-kana conversion via Yahoo! JLP. 31 endpoints total. No authentication required for MCP. Pay-per-call $0.02/call viaMIT
- AlicenseNot gradedqualityDmaintenanceEnables access to Japanese stock market data via the free J-Quants API, providing tools for company search, daily quotes, and financial statements.1MIT
- AlicenseAqualityBmaintenanceMCP server for Japanese public business data, enabling AI agents to validate and look up corporate numbers, search bank/branch codes, and check national holidays. Runs locally with no telemetry; live corporate registry data requires a free NTA app ID.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching for Japanese companies and retrieving their securities filings from Japan's Financial Services Agency, including daily filing lists and historical filing ranges for specific filers.370 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: single verification, batch verification, shareholder lookup, and name-to-number resolution. The single-vs-batch pair is explicitly differentiated by input cardinality and pricing limits, so there is no realistic misselection.
All names use consistent snake_case with a verb_noun structure (verify_..., get_..., find_...). The only deviation is pluralization in verify_japanese_companies_batch, which is natural and readable rather than inconsistent.
Four focused tools fit a narrow verification domain well; each earns its place with no redundant surface. The single/batch split is justified by the metered per-lookup pricing model.
The surface covers the core lifecycle: resolve a name to a number, verify registration/invoice status, batch-verify, and retrieve shareholders. Minor gaps remain (no richer company profile or historical status-change endpoint), but the primary workflows have no dead ends.