Home / MCP registry index / io.usefulapi/localazy
Localazy MCP by usefulapi
io.usefulapi/localazy in the official MCP registry.
Endpoint https://localazy.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Localazy projects, files, keys and glossary; submit translations, import keys, AI suggestions.
We read its 17 tools on 2026-10-26. 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
localazy_list_projects localazy_list_import_formats localazy_list_files localazy_get_file_keys localazy_list_key_links localazy_list_cdn_metadata localazy_get_import_progress localazy_get_tm_suggestions localazy_get_mt_suggestions localazy_list_glossary localazy_get_glossary_term localazy_create_glossary_term localazy_update_glossary_term localazy_submit_translation localazy_import_keys localazy_update_key_properties localazy_translate_with_ai
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-localazy)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.