Airylark Translation

Created By
wizda year ago
Overview

What is Airylark Translation?

Airylark Translation is a professional-grade translation server module that provides high-precision translation services through the ModelContextProtocol (MCP). It allows intelligent assistants to interact with external services for complex translation tasks.

How to use Airylark Translation?

To use Airylark Translation, set up the server by installing Node.js and npm, configure the environment variables, and then run the server. You can integrate it with AI assistants that support MCP protocol for seamless translation services.

Key features of Airylark Translation?

  • Three-stage translation process: analysis, segment translation, and full proofreading.
  • Domain-specific terminology recognition for consistency.
  • Comprehensive translation quality assessment.
  • Multi-language support including Chinese, English, Japanese, Korean, French, and German.
  • Style and format preservation based on text type.

Use cases of Airylark Translation?

  1. Translating technical documents like software and API documentation.
  2. Translating academic papers while maintaining academic style.
  3. Translating legal documents with precise terminology.
  4. Translating medical materials with professional medical terminology.
  5. Translating financial reports with accurate financial concepts.

FAQ from Airylark Translation?

  • What languages does Airylark Translation support?

It supports multiple languages including Chinese, English, Japanese, Korean, French, and German.

  • How do I deploy the server?

You can deploy it using Docker or Docker Compose for easy management.

  • Is there a quality assessment feature?

Yes, it provides a detailed quality assessment of translations.

Server Config

{
  "mcpServers": {
    "airylark-translation": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TRANSLATION_API_KEY",
        "-e",
        "TRANSLATION_MODEL",
        "-e",
        "TRANSLATION_BASE_URL",
        "wizdy/airylark-mcp-server"
      ],
      "env": {
        "TRANSLATION_API_KEY": "<YOUR_API_KEY>",
        "TRANSLATION_MODEL": "<YOUR_MODEL>",
        "TRANSLATION_BASE_URL": "<YOUR_API_URL>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wizd
Star
-
Language
-
License
-

Recommend Servers

View All
Datagrout

11 hours ago
Pipeworx

12 hours ago
Datagrout

11 hours ago
Verify Action
@Armada735

Verify AI agent tool calls with content-addressed, HMAC-attested receipts. Free third-party verification API for AI agents. Call verify_action(claim, evidence) to get an independent integrity check on whether your claimed action matches the actual evidence. Useful for catching silent failures: incorrect SQL operations, file-op mismatches, API call inconsistencies, and code-diff scope creep. Five specialized verifier kinds: - code_diff: verb / path / identifier coherence with unified diff - db_op: row delta + SQL operation + ID match - file_op: existence state + line/size delta - api_call: request body and response status coherence - generic: conservative fallback Returns: - aar_verdict: verified | contradicted | insufficient_evidence | unsafe_to_verify - verdict: ok | mismatch | uncertain (legacy 3-value alias) - reasoning, confidence - receipt: verify_action_receipt.v0 with HMAC-SHA256 signature, content-addressed via SHA-256 hashes of claim and evidence Cross-vendor: works with Claude Code, Cursor, Cline, Codex, Codeium, and any MCP-compatible harness. Stateless, per-request, no API key, no registration. Pure Python stdlib (no pip install). Anonymized telemetry only — no PII, no model fingerprint, no raw claim/evidence retention. Honest scope: this is a small reference implementation, not a canonical inter-vendor standard. v0 receipts use HMAC-SHA256 (symmetric, single-issuer); v1 with ed25519 + multi-issuer is on the roadmap. The hosted endpoint has no SLA — self-host for stability (git clone && ./start.sh). 90-day probe with explicit kill criteria. If adoption appears, v1 schema work begins. If response is null, the null is itself a publishable data point.

21 hours ago