QACAT

io.github.dimawin22Published by GitHub account dimawin22v1.0.0Updated Oct 24, 2026

Translation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

QACAT is a remote MCP server for translation quality assurance, giving an assistant automated checks, AI evaluation, linguistic review and visual in-context QA.

What you can do
Run automated translation quality checks on translated content, per the registry description of automated checks and AI evaluation. Perform AI-based evaluation of translations. Support linguistic review of translated material. Carry out visual in-context testing of translations as they appear in context. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when an assistant is helping review or validate translations and you want quality checks, AI evaluation and in-context visual testing available as tools rather than manual steps.
Requirements
A remote streamable HTTP endpoint at qacat-mcp.qacat.workers.dev. A QACAT API key (qct_live_...) sent as a bearer token in the Authorization header is required. Network access to the endpoint is needed.
Before you install
The server requires a QACAT API key sent in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. The manifest does not describe what content is sent to the service or whether operations change data, so review the provider's terms before use.

Installation

In SourceWeft

  1. Open QACAT in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.dimawin22%2Fqacat/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "qacat": {
      "type": "http",
      "url": "https://qacat-mcp.qacat.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.