Developer · Remote MCP server
QACAT
Translation QA: automated checks, AI evaluation, linguistic review, and visual in-context testing.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dimawin22/qacat- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-21
- Updated
- 2026-07-21
- Publisher
- dimawin22 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dimawin22) · how
- Website
- qacat.alconost.com
- Repository
- github.com/alconost/qacat-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://qacat-mcp.qacat.workers.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect QACAT
QACAT is a remote MCP server: there is nothing to install. Its endpoint is https://qacat-mcp.qacat.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Python Docs MCP ServerThe canonical Python stdlib oracle for AI coding agents - always free, always MIT, token-frugal. | Local · stdio |
| Python Exec SandboxSandboxed Python execution for AI agents. PEP 723 inline deps, multi-version Python, zero pollution. | Local · stdio |
| q-ringOS keychain secrets for AI coding agents, over MCP. | Local · stdio |
| QA RadarTells AI agents which files to test first - churn, coverage, and test mapping as risk scores. | Local · stdio |
| Qai Consultant MCPKeyless local MCP server for QA: standards retrieval, effort estimation, doc review, test analysis. | Local · stdio |
| QarunbookShared app-testing runbook: read the plan, record results per platform, raise and fix issues. | Remote · HTTPLive check: sign-in required |
| QaskillsSearch, inspect, and install 400+ QA testing skills from qaskills.sh into any MCP client. | Local · stdio |
| QatouchMCP Server for software testing, test case management, test execution, and defect tracking. | Local · stdio |