F
licenseNot graded
qualityD
maintenanceMCP server for the HY-MT translation model, allowing AI assistants to perform high-quality translations across 38 languages via the Model Context Protocol.
5
-
MCP-Serve 多语言翻译服务
by oofengoo
Related Servers
Alternatives to MCP-Serve 多语言翻译服务
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAI-powered translation MCP server with EU AI Act compliance, enabling automated translation workflows via the MCP protocol.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides standardized translation services across six languages (Arabic, Chinese, English, French, Russian, Spanish) using Claude Sonnet 3.5, with support for different domains and formality levels.3MIT
- AlicenseNot gradedqualityDmaintenanceAn AI-driven text translation service supporting 20+ languages, based on the Model Context Protocol (MCP) for integration with Claude Desktop and other MCP-compatible applications.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive localization data for 174 locales, enabling AI agents to generate culturally-adapted multilingual content.MIT
- AlicenseAqualityBmaintenanceMCP server for AI-powered translation management in i18n projects, enabling automated locale detection, translation status checks, and sync via LangAPI.430 npm1MIT
TDQS
D1.2/5.0
Scored across 2 tools
Disambiguation1/5
The two tools have overlapping purposes with no descriptions to clarify differences. 'copyI18n' and 'translationI18n' both appear to handle i18n (internationalization) tasks, making them indistinguishable. An agent cannot determine when to use one versus the other, leading to high misselection risk.
Naming Consistency3/5
The naming shows mixed conventions: 'copyI18n' uses camelCase while 'translationI18n' uses a similar style but with a different prefix. Both include 'I18n', providing some thematic consistency, but the lack of a clear verb_noun pattern and the variation in prefixes ('copy' vs. 'translation') reduces predictability.
Tool Count2/5
With only 2 tools for a '多语言翻译服务' (multilingual translation service), the count feels too thin. A translation service typically requires more operations, such as translate_text, detect_language, or manage_translations. This minimal set limits functionality and suggests an incomplete implementation.
Completeness1/5
The tool surface is severely incomplete for a translation service. There are no tools for core operations like translating text, detecting languages, or managing translation keys. The two vague tools do not cover the domain's essential workflows, leaving significant gaps that will cause agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues