Ext Ops Panel
Open dashboard
Comparison

DevSpeak vs io.github.mrslbt/japan-ux

DevSpeak is an MCP server published by juanjaragavi. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrslbt/japan-ux is an MCP server published by mrslbt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
MarketplaceDevSpeakio.github.mrslbt/japan-ux
Official MCP Registry Listed
Version: 1.3.1
Downloads/month (npm): 95
Downloads/week (npm): 20
Not marked · First seen
Listed
Version: 2.1.1
Downloads/month (npm): 522
Downloads/week (npm): 39
Forks (GitHub): 0
Stars (GitHub): 0
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

DevSpeak vs io.github.mrslbt/japan-ux
FactDevSpeakio.github.mrslbt/japan-ux
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)2026-10-24Not published
Where it runs (differs)Remote server (www.devspeak.dev/mcp)On your machine (japan-ux-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/mrslbt/japan-ux-mcp
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 8 h ago, requires a keyno 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

DevSpeak

In its own words, on Official MCP Registry:

Improve or correct developer writing, or turn rough notes into technical specs, from your agent.

io.github.mrslbt/japan-ux

In its own words, on Official MCP Registry:

Japanese UI + UX correctness for AI coding agents — typography, forms, keigo, JLReq checks.

How to run each

DevSpeak As a remote MCP server

Claude Code
claude mcp add --transport http devspeak https://www.devspeak.dev/mcp --header "x-api-key: <YOUR_X_API_KEY>"

Requires: DEVSPEAK_API_KEY (secret), x-api-key header

io.github.mrslbt/japan-ux As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio japan-ux -- npx -y japan-ux-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only DevSpeak 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

The marketplaces of io.github.mrslbt/japan-ux publish no settings it asks for, so we do not compare settings.

What it can do: DevSpeak · What it can do: io.github.mrslbt/japan-ux · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built