Home / MCP registry index / io.usefulapi/weblate
Weblate MCP by usefulapi
io.usefulapi/weblate in the official MCP registry.
Endpoint https://weblate.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Weblate projects, strings, stats and changes; translate, suggest, comment and autotranslate.
We read its 23 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
weblate_list_projects weblate_get_project weblate_list_components weblate_get_component weblate_list_translations weblate_get_translation weblate_get_statistics weblate_list_project_languages weblate_list_languages weblate_list_units weblate_get_unit weblate_list_unit_comments weblate_list_suggestions weblate_list_changes weblate_search_memory weblate_lookup_memory weblate_get_repository_status weblate_update_translation weblate_add_suggestion weblate_accept_suggestion weblate_add_unit_comment weblate_repository_operation weblate_autotranslate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-weblate)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.