io.github.mrslbt/japan-ux
NPM · JAPAN-UX-MCP
Japanese UI + UX correctness for AI coding agents — typography, forms, keigo, JLReq checks.
Available components
Last scanned (15 hours ago)
Scores higher than 89% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2112 tokens (~105/item across 20 items; 11 tools + 9 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Analysed npm/japan-ux-mcp@2.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_japan_ux Audit Japan UX ~183
Comprehensive Japanese UX audit covering 7 categories: layout (density, breadcrumbs, CTA placement), typography (fonts, line-height, kinsoku shori), visual (color meanings, red-name taboo, dark theme), navigation (phone number, footer links, hamburger rules), trust (会社概要, case studies, proof numbers, legal links), content (Japanese text, FAQ, pricing tables), and mobile (viewport, tel: links, touch targets). Returns letter grade (A-F), category scores, and prioritized fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| css | string | – | CSS content for typography and visual checks |
| markup | string | yes | HTML/JSX markup to audit |
| site_type | string | yes | Type of site being audited |
| target_audience | string | – | Target audience description |
| url_description | string | – | Description of the page for additional context |
No output schema declared.
No examples provided.
check_jp_typography Check JP Typography ~165
Audit CSS and markup for Japanese typography issues. Checks: font stacks (Noto Sans JP, Hiragino, Yu Gothic), line-height (1.7-2.0 for Japanese body text), font sizes (14px body minimum, 12px captions floor), kinsoku shori (line-break: strict), text-on-photo overlays, font-feature-settings 'palt' on headings, font-synthesis, and more. Returns score, issues, and a recommended font stack for your context.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Design context for font stack recommendation |
| css | string | yes | CSS content to audit for Japanese typography issues |
| markup | string | – | Optional HTML/JSX markup for additional context (background images, text-on-photo detection) |
No output schema declared.
No examples provided.
design_direction_for_japan Design Direction for Japan ~154
Generate a Japan-specific visual direction for a website or interface. Takes a loose brand type, audience, and industry, then returns a practical design brief covering visual direction, information density, color palette, typography, imagery style, CTA style, trust layout, and section priorities.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | yes | Target audience such as 'business buyers', 'families', 'seniors', 'domestic travelers' |
| brand_type | string | yes | Brand expression such as 'modern minimal', 'premium', 'friendly', 'traditional craft' |
| industry | string | yes | Industry or site type such as 'B2B SaaS', 'clinic', 'luxury ryokan', 'ecommerce', 'corporate' |
No output schema declared.
No examples provided.
generate_jp_form Generate JP Form ~143
Generate culturally correct Japanese form markup with proper field order (姓→名), furigana, 3-field phone, 〒 postal address, 年月日 dates, and context-appropriate keigo. Use this when building any form for a Japanese audience.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Business context — determines keigo politeness level |
| fields | array | yes | Fields to include in the form |
| format | string | – | Output format |
| include_labels | boolean | – | Include field labels |
| include_validation | boolean | – | Include validation patterns |
| language | string | – | Label language |
| type | string | yes | Type of form to generate |
No output schema declared.
No examples provided.
generate_jp_placeholder Generate JP Placeholder Data ~130
Generate realistic Japanese test data for prototypes and development. Returns names (kanji + katakana furigana + romaji), addresses (real postal codes and prefectures), phone numbers (correct 3-field format), company names, and dates (both Gregorian and Japanese era format like 平成4年3月15日).
| Name | Type | Req | Description |
|---|---|---|---|
| age_range | string | – | Age range like "20-40" for date_of_birth generation |
| count | number | – | Number of records to generate |
| fields | array | yes | Data fields to include |
| gender | string | – | Gender for name generation |
No output schema declared.
No examples provided.
get_seasonal_context Get Seasonal Context ~132
Get the current Japanese seasonal context for design decisions. Returns: current season with traditional colors, active events (正月, 花見, お盆, etc.), upcoming events, the current microseason (二十四節気), recommended design colors, and warnings (e.g., do not launch during Golden Week). Covers all 24 Japanese microseasons and 24+ major events.
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | – | Day of month. Defaults to today when month is omitted, else 15. |
| month | number | – | Month (1-12). Defaults to the current month (server local time). |
No output schema declared.
No examples provided.
review_jp_ui Review JP UI ~138
Review CSS/markup against the Japanese UI standard (typography, colour, font performance) and return a pass/needs_work/fail verdict with violations, JLReq/JIS citations, and fixes. The front-end correctness enforcer — run on any UI (including Western-built) before shipping to Japan; call transform_for_japan to auto-apply form/copy fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Design context for the recommended font stack. |
| css | string | yes | CSS content to review against the Japanese UI standard. |
| markup | string | – | Optional HTML/JSX markup for context (e.g. text-on-photo detection). |
No output schema declared.
No examples provided.
score_japan_readiness Score Japan Readiness ~155
Score any page or component for Japan-readiness on a 0-100 scale. Analyzes 5 categories: forms (name order, furigana, phone, postal), copy (keigo, Japanese text, placeholders), trust (特定商取引法, phone number, company info), typography (font, size, line-height), and cultural (seasonal awareness, imagery). Returns breakdown with issues and quick wins per category.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Business context |
| description | string | – | Description of the page/component for additional context |
| include_suggestions | boolean | – | Include priority fix suggestions with impact estimates |
| markup | string | yes | HTML/JSX markup to analyze |
No output schema declared.
No examples provided.
suggest_keigo_level Suggest Keigo Level ~127
Suggest appropriately polite Japanese UI text based on context. Maps business context to keigo level (casual → very_formal) and returns the right Japanese translation for buttons, error messages, empty states, confirmations, and more. Includes alternatives for different formality levels.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Business context — determines keigo level |
| text | string | yes | English UI text to translate (e.g. 'Invalid email address', 'Submit', 'No results found') |
| tone | string | – | Optional tone override |
| ui_element | string | yes | Type of UI element |
No output schema declared.
No examples provided.
transform_for_japan Transform for Japan ~138
Transform Western markup into Japan-ready markup. Automatically fixes: name field order (firstName/lastName → 姓/名), adds furigana, splits phone into 3 fields, restructures address to 〒 postal format, translates buttons with appropriate keigo, replaces Western placeholder data with Japanese examples. Shows before/after scores and explains every change.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Business context — determines keigo level and conventions |
| format | string | – | Output format |
| markup | string | yes | Western HTML/JSX markup to transform |
| preserve_styling | boolean | – | Preserve existing CSS classes and styles |
No output schema declared.
No examples provided.
validate_jp_form Validate JP Form ~100
Audit an existing form against Japanese UX conventions. Checks for: name field order (姓/名), furigana, 3-field phone, postal code auto-fill, keigo-appropriate button text, full-width character handling. Returns score (0-100), issues with fixes, and what passed.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Business context for keigo expectations |
| form_markup | string | yes | HTML/JSX form markup to audit |
No output schema declared.
No examples provided.
How do I install the io.github.mrslbt/japan-ux MCP server?
io.github.mrslbt/japan-ux runs locally as an npm package, launched with npx -y japan-ux-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · japan-ux-mcp
claude mcp add mrslbt-japan-ux -- npx -y japan-ux-mcp
What is the io.github.mrslbt/japan-ux MCP server?
io.github.mrslbt/japan-ux is an MCP server listed in the public MCP registry as io.github.mrslbt/japan-ux. Japanese UI + UX correctness for AI coding agents, typography, forms, keigo, JLReq checks. This page covers its npm package (japan-ux-mcp).
Is the io.github.mrslbt/japan-ux MCP server safe to use?
io.github.mrslbt/japan-ux scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mrslbt/japan-ux MCP server expose?
io.github.mrslbt/japan-ux exposes 11 tools: review_jp_ui, generate_jp_form, validate_jp_form, generate_jp_placeholder, suggest_keigo_level, and 6 more. Their descriptions and schemas cost roughly 1,565 tokens of context every time the server is loaded.
Is the io.github.mrslbt/japan-ux MCP server still maintained?
io.github.mrslbt/japan-ux is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mrslbt/japan-ux MCP server under?
io.github.mrslbt/japan-ux declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrslbt/japan-ux MCP server?
VerifyMCP ran 16 checks on io.github.mrslbt/japan-ux, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.