locli
NPM · @LOCLI/CLI
Find, add, push and pull an app's user-facing texts in locli (iOS, Android, web, backend).
Available components
Last scanned (6 hours ago)
Scores higher than 40% of npm servers
Category Documents and Files
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1428 tokens (~129/item across 11 items; 11 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +16
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 1269 → 1428 ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Destructive annotations: pass → 100 functional
- Package version: 0.1.9 → 0.1.10 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 998 → 1269 ▼ functional
- Package version: 0.1.6 → 0.1.9 functional
- Package version: 0.1.6 → 0.1.7 functional
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.1.5 → 0.1.6 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 814 → 998 ▼ functional
- Package version: 0.1.3 → 0.1.5 functional
- 29 Oct 26 69
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@locli/cli@0.1.10
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
locli_add_texts Add texts ~186
Create missing keys and values in locli. Never overwrites: values that already exist are reported as skipped (change them in locli instead). Use lower_snake_case keys whose first segment is the feature area and always give a comment saying where the text appears and what each placeholder holds. Placeholders are printf style (%@, %lld, %1$@) for iOS/Android, ICU names ({used}, {n, number}) for keys used only on web/backend; give plural texts as forms with "other". New keys join the current Git branch's feature. Prefer adding the text to the app's source file and calling locli_push when the app has one.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Git branch for feature grouping (default: detected). |
| dryRun | boolean | – | Only report what would be added. |
| texts | array | yes | – |
No output schema declared.
No examples provided.
locli_areas Feature areas ~111
The project's feature areas (a key's first segment, e.g. login in login_username_label) with key counts and examples. With feature="login" it returns the existing area to use (by name or synonym such as auth/signin) or proposes a new one, which the first push of keys with that prefix creates. Call it when you start building a feature. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| feature | string | – | The feature you are building, e.g. "login" or "receipt import". |
No output schema declared.
No examples provided.
locli_community_review Review a community suggestion ~123
Decide one community suggestion: accept makes it the working text (it ships with the next approved release; you never approve releases), reject declines it, hide removes spam or abuse from the public page. Before accepting, check that placeholders, the glossary (locli_guide) and the tone fit; when several suggestions compete, prefer the clearly better wording, not only the score.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | – |
| id | string | yes | Suggestion id from locli_community_suggestions. |
| note | string | – | Why, visible to the team. |
No output schema declared.
No examples provided.
locli_community_suggestions Community suggestions ~100
Suggestions from the project's public community catalog (anyone can suggest translations of released texts, vote and discuss, without an account), the most voted first. Each has an id, key, language, source text, today's text in locli, the suggestion, score, votes and the public discussion. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Only this language, e.g. "fr". |
| status | string | – | Default: open. |
No output schema declared.
No examples provided.
locli_context Where texts are used ~151
Scans the app's code for every key in locli.json's files: where it is used (file:line), as what (toolbar item, tab, button, menu item, screen title, form field, push notification, email, alert, error message, accessibility label, text) and its length budget in characters. Lists translations in the files that exceed their budget and keys not found in the code. Call it before translating and fix every too-long text (shorter wording, or a layout that wraps). Local, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Only this key, or every key of this area (e.g. "auth"). |
| target | string | – | Only this platform. |
No output schema declared.
No examples provided.
locli_delete_keys Delete unreleased keys ~159
Delete keys that no release ever contained: in locli (texts, translations, history) and in the app files from locli.json, so the next push does not add them back. Keys locli does not know are removed from the files only. If any key was already released, nothing is deleted: apps may still show it, so a project owner deletes it in the web editor. Warns about code that still uses a deleted key. Use for duplicates, typos and texts of a feature that was dropped; run with dryRun first and show the user the list.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Only report what would be deleted. |
| keys | array | yes | Key names, e.g. ["adminDashboard_location"]. |
No output schema declared.
No examples provided.
locli_find_texts Find existing texts ~92
Search existing keys, translator comments and values (case-insensitive, all words must match). Call this before creating a key so a text with the same meaning is reused. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Only search and show this language, e.g. "de". |
| query | string | yes | Words from the text or key, e.g. "sign in" or "receipt_count". |
No output schema declared.
No examples provided.
locli_guide Translation guide ~55
The project's translation guide: tone and form of address per language, glossary terms with their required translation, terms that stay as written (keep), and every current translation that breaks the glossary. Read it before translating. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locli_pull Pull approved texts ~69
Write the latest approved release into the app files from locli.json. Replaces the released keys' texts in those files; local-only keys stay. draft=true writes the unapproved working state for local checks only.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | boolean | – | – |
| target | string | – | Only this platform. |
No output schema declared.
No examples provided.
locli_push Push new texts ~75
Upload texts from the app files in locli.json that locli lacks (new keys, missing languages). Never overwrites existing texts. Reports how many texts wait for a release.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | Only print the plan. |
| target | string | – | Only this platform (ios, android, web, backend). |
No output schema declared.
No examples provided.
locli_status locli status ~39
Project overview from locli.json: languages, missing texts per language, open Git features and whether unreleased changes wait for release approval. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the locli MCP server?
locli runs locally as an npm package, launched with npx -y @locli/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @locli/cli
claude mcp add mariohahn-locli -- npx -y @locli/cli
What is the locli MCP server?
locli is an MCP server listed in the public MCP registry as io.github.mariohahn/locli. Find, add, push and pull an app's user-facing texts in locli (iOS, Android, web, backend). This page covers its npm package (@locli/cli).
Is the locli MCP server safe to use?
locli scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 locli MCP server expose?
locli exposes 11 tools: locli_status, locli_areas, locli_guide, locli_context, locli_find_texts, and 6 more. Their descriptions and schemas cost roughly 1,160 tokens of context every time the server is loaded.
Is the locli MCP server still maintained?
locli is still listed as active in the MCP registry. We last reached this channel on 5 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 locli MCP server under?
locli declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.