Ext Ops Panel
Open dashboard
Comparison

rtl-chat vs Korean Address to English — Convert & Validate (주소 영문)

rtl-chat is a plugin bundle for AI coding tools published by MSApps-Mobile. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Korean Address to English — Convert & Validate (주소 영문) is an MCP server published by kr-data-api. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacertl-chatKorean Address to English — Convert & Validate (주소 영문)
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

rtl-chat vs Korean Address to English — Convert & Validate (주소 영문)
Factrtl-chatKorean Address to English — Convert & Validate (주소 영문)
Marketplaces that list it11
Stars (GitHub) (differs)9No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.apify.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/msapps-mobile/claude-pluginsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

rtl-chat

In its own words, on Claude Code: claude-plugins-community:

Ensures Claude's chat responses are properly formatted for Hebrew RTL (right-to-left) text, especially when mixing Hebrew and English. Handles bidirectional text formatting so responses look clean and readable instead of jumbled. Should be active on every response when the conversation includes Hebrew text.

Korean Address to English — Convert & Validate (주소 영문)

In its own words, on Official MCP Registry:

Korean addresses to official English: road address, postal code, romanized unit; validated vs gov DB

How to run each

rtl-chat As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install rtl-chat@claude-community

Korean Address to English — Convert & Validate (주소 영문)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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: rtl-chat · What it can do: Korean Address to English — Convert & Validate (주소 영문) · 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. 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