LingoHub MCP by usefulapi
REMOTE · LINGOHUB.USEFULAPI.IO
MCP server for LingoHub — localization projects, resources, exports and repository pushes.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
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 6 Nov 2026 · Probed https://lingohub.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lingohub.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lingohub.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lingohub/ |
| http (plaintext) | http://lingohub.usefulapi.io/mcp | Inconclusive | 302 | http://lingohub.usefulapi.io/mcp |
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 →
lingohub_create_project Create project ~199
WRITE: create a new localization project in a workspace (needs settings-management permission on the key). Returns the new project with its links. It adds a project and changes nothing existing; repeating the call can create a second project. POST /v1/{workspace_url}/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description, up to 512 characters. |
| resource_type | string | yes | Resource file type, which fixes the import/export format (e.g. standard_json, i18next_json, android_xml, ios_strings, gettext_po, xliff). |
| source_language | string | yes | Source language code, e.g. en or en-GB. |
| target_languages | array | – | Target language codes, e.g. ["de","fr"]. |
| title | string | yes | Project title. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_delete_context_image Delete context image ~133
WRITE, DESTRUCTIVE: delete one context image and its connections to text segments. Never retried. DELETE .../projects/{project_url}/contextImages/{image_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| image_id | string | yes | Context image id from list_context_images, e.g. ci_18USq6822XIv-19847171. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_delete_resource Delete resource file ~185
WRITE, DESTRUCTIVE: delete a resource container: the source-language file AND all its target-language files with their translations. file_name and path must address the source-language file. This cannot be undone through the API. Never retried. DELETE .../projects/{project_url}/resources/{file_name}.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| file_name | string | yes | File name of the SOURCE-language file, as list_resources shows it. |
| path | string | – | Folder of the source-language file. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_download_resource Download resource file ~273
Download one resource file as text, in one language. file_name is the file name as list_resources shows it (the folder goes in `path`). Long files are cut at 40000 characters (truncated: true); use request_export for a full copy. GET .../projects/{project_url}/resources/{file_name}.
| Name | Type | Req | Description |
|---|---|---|---|
| blank_content_handling | string | – | What to export for a segment with no translation in the target language. |
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| file_name | string | yes | Resource file name, e.g. messages_de.properties. |
| filter_by_status | string | – | Only export target segments in this state. |
| html_encoding | string | – | How HTML in a segment is escaped. |
| language | string | – | Locale code to export (overrides the locale in the file name), e.g. de. |
| path | string | – | Folder of the file, when the file name alone is not unique. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_get_export Get export status ~157
Status of an export started with request_export: overall and per-file status (NEW, SCHEDULED, PROCESSING, SUCCESS, SKIPPED, ERROR), error details and, when done, the pre-signed download URL of the ZIP. GET .../projects/{project_url}/exports/{export_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| export_id | string | yes | Export id from request_export, e.g. reg_18USq6822XIv-19847171. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_get_project Get project ~99
One project: title, description, owner email, configured locales (project_locales), timestamps and links. GET /v1/{workspace_url}/projects/{project_url}.
| Name | Type | Req | Description |
|---|---|---|---|
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_get_project_status Get project file status ~155
Translation status of one project: each resource file with per-locale segment counts (NOT_TRANSLATED, DRAFT, TRANSLATED, APPROVED, ...), failing quality checks, the export formats it supports and whether a Git repository is connected and can be pushed to. GET .../projects/{project_url}/status.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_get_workspace_status Get workspace translation status ~94
Translation progress of every project in one workspace: title, app URL, total segment count and per-locale counts by status (NOT_TRANSLATED, DRAFT, TRANSLATED, PREFILLED, APPROVED). GET /v1/{workspace_url}/projects/status.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_list_context_images List context images ~144
List the context images (screenshots that show translators where a text is used) of a project, with connected-segment counts and processing status. Paginated; page is zero-based. GET .../projects/{project_url}/contextImages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-based page index (default 0). |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| size | integer | – | Results per page, 1-100. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_list_projects List projects ~60
List every Lingohub project this API key can see (owned and shared, across workspaces). Each entry has the title, its links and the workspace_url + project_url slugs that every other tool needs. GET /v1/projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lingohub_list_resources List resource files ~164
List a project's resource files: name, locale and links (including a download link). GET .../projects/{project_url}/resources.
| Name | Type | Req | Description |
|---|---|---|---|
| add_iso2_slug | boolean | – | Always add the iso2_slug parameter to the rendered file URLs. |
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| locale_in_file_name | string | – | Whether file names carry the locale: ALL (default), TARGETS or NONE. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_push_to_repository Push translations to repository ~287
WRITE: push the project's resource files to its linked Git repository (GitHub, GitLab, Bitbucket or Azure DevOps; the connection must already exist). Depending on push_type this commits to a branch or opens a pull request, so it changes the user's repository. Never retried. POST .../projects/{project_url}/push.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch to push to. Default: the repository connection's default branch. |
| commit_description | string | – | Extended commit description. |
| commit_message | string | – | Commit message. Default: generated. |
| language | string | – | Only push this language. |
| path | string | – | Only push resource files under this path. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| pull_request_branch | string | – | Branch to create for the pull request (PULL_REQUEST only). |
| pull_request_description | string | – | Pull request description (PULL_REQUEST only). |
| pull_request_title | string | – | Pull request title (PULL_REQUEST only). |
| push_type | string | – | PUSH commits directly; PULL_REQUEST opens a pull/merge request. Default: the connection's setting. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_request_export Request export ~223
Start an asynchronous export of a project's resource files as a ZIP. It creates an export job and changes no project data. Returns the export id; poll get_export until its status is SUCCESS to get the download URL. Without filters it exports every file and language. POST .../projects/{project_url}/exports.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| export_format | string | – | Override the export format of the project type. |
| file_paths | array | – | Only these files, with the locale placeholder as shown in Lingohub, e.g. config/locales/%{locale}/messages.yml. |
| languages | array | – | Only these language codes, e.g. ["en","de"]. |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
lingohub_upload_resource_file Upload resource file ~407
WRITE: upload one text resource file (JSON, properties, XLIFF, PO, ...) into a project. The language comes from the file name or from `language`. The import flags decide whether existing segments are changed or deactivated: with updating or deactivation on, translations already in Lingohub can be overwritten or switched off, so state the flags you want. Never retried. POST .../projects/{project_url}/resources.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Project branch name. Default: the project's default branch. An unknown branch is HTTP 422. |
| content | string | yes | The file text (UTF-8), up to 1000000 characters. |
| file_name | string | yes | File name with extension, e.g. en.json. |
| language | string | – | Locale of this file (overrides the locale in the file name), e.g. de. |
| path | string | – | Folder the file is uploaded to; set it when the file name collides with another file (HTTP 406). |
| project_url | string | yes | Project URL slug (e.g. "feature-demo"); list_projects returns it as project_url. |
| source_create_new | boolean | – | If this is a source-language file: create new segments. |
| source_deactivate_missing | boolean | – | If this is a source-language file: deactivate segments missing from the file. |
| source_update_existing | boolean | – | If this is a source-language file: update changed segments. |
| target_create_new | boolean | – | If this is a target-language file: create new segments. |
| target_deactivate_missing | boolean | – | If this is a target-language file: deactivate segments missing from the file. |
| target_update_existing | boolean | – | If this is a target-language file: update changed translations (overwrites existing ones). |
| workspace_url | string | yes | Workspace URL slug (e.g. "lingohub-demo"); list_projects returns it as workspace_url. |
No output schema declared.
No examples provided.
How do I install the LingoHub MCP by usefulapi server?
LingoHub MCP by usefulapi is a hosted endpoint at https://lingohub.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lingohub.usefulapi.io
claude mcp add --transport http io-usefulapi-lingohub 'https://lingohub.usefulapi.io/mcp'
What is the LingoHub MCP by usefulapi server?
LingoHub MCP by usefulapi is listed in the public MCP registry as io.usefulapi/lingohub. MCP server for LingoHub, localization projects, resources, exports and repository pushes. This page covers its hosted endpoint (https://lingohub.usefulapi.io/mcp).
Is the LingoHub MCP by usefulapi server safe to use?
LingoHub MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 LingoHub MCP by usefulapi server expose?
LingoHub MCP by usefulapi exposes 14 tools: lingohub_list_projects, lingohub_get_project, lingohub_get_project_status, lingohub_get_workspace_status, lingohub_create_project, and 9 more. Their descriptions and schemas cost roughly 2,580 tokens of context every time the server is loaded.
Does the LingoHub MCP by usefulapi server require authentication?
Its publisher declares no required credentials for LingoHub MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the LingoHub MCP by usefulapi server still maintained?
LingoHub MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the LingoHub MCP by usefulapi server?
VerifyMCP ran 4 checks on LingoHub MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about LingoHub MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.