Ext Ops Panel
Open dashboard
Comparison

Lara Translate vs APICK

Lara Translate is an MCP server published by translated. Marketplaces we read that list it: 1 (Docker MCP Catalog). APICK is an MCP server published by apick.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplaceLara TranslateAPICK
Docker MCP Catalog Listed
Version: sha256:0424253c6b8f
Forks (GitHub): 22
Pulls (Docker Hub): 19 014
Stars (Docker Hub): 3
Stars (GitHub): 99
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.6.1
Downloads/month (npm): 4 656
Downloads/week (npm): 1 349
Forks (GitHub): 0
Stars (GitHub): 1
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

Lara Translate vs APICK
FactLara TranslateAPICK
Marketplaces that list it11
Stars (GitHub) (differs)99 (better)1 (worse)
Pulls (Docker Hub) (differs)19 014No figure on Docker Hub
Forks (GitHub) (differs)22 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/lara)Remote server (apick.app/mcp/all)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)22Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/translated/lara-mcpgithub.com/lead788/apick-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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

Lara Translate

In its own words, on Docker MCP Catalog:

Connect to Lara Translate API, enabling powerful translation capabilities with support for language detection and context-aware translations.

APICK

In its own words, on Official MCP Registry:

APICK Korean data, simple-auth lookups, OCR, search, conversion, image, video and TTS

How to run each

Lara Translate As a local MCP server: Docker image

Claude Code
claude mcp add --env "LARA_ACCESS_KEY_SECRET=<YOUR_LARA_ACCESS_KEY_SECRET>" --transport stdio lara -- docker run -i --rm -e LARA_ACCESS_KEY_SECRET mcp/lara

Requires: LARA_ACCESS_KEY_SECRET (secret)

APICK As a remote MCP server

Claude Code
claude mcp add --transport http all https://apick.app/mcp/all --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: APICK_API_KEY (secret), Authorization header

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

Only APICK has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of APICK publish no list of tools, so we do not compare tools.

Settings each asks for

Only Lara Translate asks for

  • LARA_ACCESS_KEY_ID
  • LARA_ACCESS_KEY_SECRET (secret)

Only APICK asks for

  • APICK_API_KEY (secret)
  • APICK_MCP_SERVER

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Lara Translate · What it can do: APICK · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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