LeashIndex Get the report

Index / devtools

io.github.qatouch/qatouch

io-github-qatouch-qatouch declares 55 capabilities across 55 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

85/100 exposureHigh exposure

Manifest recorded 2026-11-03 from tools/list answered by the npm package qatouch-mcp-server@1.1.8 (published to npm as qatouch-mcp-server, listed in the official MCP registry as io.github.qatouch/qatouch 1.1.8), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 55 tools

55 of 55 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

high · no-expiry · All 55 tools

55 of 55 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 55 tools

55 of 55 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 20 of 55 tools

20 tools can modify data and declare no limit.

low · uncapped-read · 35 of 55 tools

35 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
list_projectsread inferred
count_all_projectsread inferred
create_projectwrite inferred
list_test_casesread inferred
count_test_casesread inferred
list_test_runsread inferred
count_test_runsread inferred
list_test_run_resultsread inferred
list_test_run_result_historyread inferred
list_test_run_statusesread inferred
update_test_run_result_statusread inferred
list_test_run_available_usersread inferred
update_test_run_results_by_codewrite inferred
create_test_run_with_moduleswrite inferred
list_modulesread inferred
count_modulesread inferred
create_modulewrite inferred
list_defectsread inferred
list_defect_statusesread inferred
list_defect_severitiesread inferred
list_defect_issue_typesread inferred
list_defect_environmentsread inferred
count_defectsread inferred
create_defectwrite inferred
list_releasesread inferred
count_releasesread inferred
create_releasewrite inferred
list_requirementsread inferred
count_requirementsread inferred
list_requirement_documentsread inferred
create_requirement_documentwrite inferred
create_requirementwrite inferred
list_workspaceread inferred
create_test_casewrite inferred
create_bulk_test_caseswrite inferred
create_exploratory_test_casewrite inferred
create_text_test_casewrite inferred
import_test_caseswrite assumed
search_test_casesread inferred
search_modulesread inferred
search_requirementsread inferred
search_defectsread inferred
search_releasesread inferred
search_projectread inferred
get_project_analyticsread inferred
update_test_casewrite inferred
get_playwright_scripts_by_projectread inferred
get_playwright_script_by_caseread inferred
get_playwright_scripts_by_moduleread inferred
generate_test_run_reportwrite assumed
generate_test_case_reportwrite assumed
generate_project_reportwrite assumed
generate_module_reportwrite assumed
generate_requirement_reportwrite assumed
generate_issue_reportwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.