Qaskills runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 30 Oct 2026.
Search, inspect, and install 400+ QA testing skills from qaskills.sh into any MCP client.
We read the source, 2 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
find . -type d -name __pycache__ -prune -exec rm -rf {} +
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Avoid mounting \`/var/run/docker.sock\` into test jobs just to launch service containers. Access to a powerful engine socket commonly permits host-level actions. If browser tests need application dependencies, provision them through the CI executor's controlled service mechanism,…
Never cache secrets written by registry authentication. Configure scoped registry tokens through masked CI variables and ensure \`.npmrc\` with interpolated credentials is not inside a cache path or artifact. Prefer short-lived credentials where the registry supports them.
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Qaskills and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add qaskills -- npx -y @qaskills/mcp
{
"mcpServers": {
"qaskills": {
"command": "npx",
"args": [
"-y",
"@qaskills/mcp"
]
}
}
}
[mcp_servers.qaskills]
command = "npx"
args = ["-y", "@qaskills/mcp"]
{
"mcpServers": {
"qaskills": {
"command": "npx",
"args": [
"-y",
"@qaskills/mcp"
]
}
}
}
{
"servers": {
"qaskills": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@qaskills/mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
QASKILLS_API_URL (Override the QASkills API base URL (defaults to https://qaskills.sh)).
Train, test, install and review a website AI agent (CAAC Go) from any MCP client.
Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.
Agentic UX testing for real Electron apps: launch, inspect, interact, and assert through MCP.
Search Grok Bot connectors, install methods, test status, and the connector wishlist.
Deterministic fault-injection server for testing how MCP clients handle failures and recover.
Check whether a Claude Code skill was tested and whether it works before installing it.
Tested AI agent skill files (SKILL.md), bought once over x402 for cents on Base. Free MCP search.
Search accredited testing labs and verify lab scope evidence from ScopeMatch.
Answers built from our own checks of this server.