LeashIndex Get the report

Index / storage

io.github.acabala/apidog-tests-mcp

io-github-acabala-apidog-tests-mcp declares 30 capabilities across 30 tools, with 2 critical issues.

85/100 exposureHigh exposure

Manifest recorded 2026-10-14 from tools/list answered by the npm package @acabala/apidog-tests-mcp@0.0.5 (published to npm as @acabala/apidog-tests-mcp, listed in the official MCP registry as io.github.acabala/apidog-tests-mcp 0.0.5), 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 30 tools

30 of 30 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.

critical · irreversible-uncapped · 5 of 30 tools

5 tools are classified as irreversible and declare no limit.

high · no-expiry · All 30 tools

30 of 30 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 30 tools

30 of 30 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 · 11 of 30 tools

11 tools can modify data and declare no limit.

low · uncapped-read · 14 of 30 tools

14 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_environmentsread inferred
list_api_endpointsread inferred
list_test_case_categoriesread inferred
list_test_case_tagsread inferred
list_runnersread inferred
get_endpoint_statisticsread inferred
list_test_casesread inferred
get_test_caseread inferred
create_test_casewrite inferred
create_test_cases_bulkwrite inferred
update_test_casewrite inferred
delete_test_casedelete inferred
list_test_scenariosread inferred
get_test_scenario_stepsread inferred
create_test_scenariowrite inferred
update_test_scenario_stepswrite inferred
delete_test_scenariodelete inferred
list_test_suitesread inferred
get_test_suiteread inferred
create_test_suitewrite inferred
update_test_suite_itemswrite inferred
delete_test_suitedelete inferred
create_scenario_folderwrite inferred
delete_scenario_folderdelete inferred
create_suite_folderwrite inferred
list_test_dataread inferred
get_test_dataread inferred
create_test_datawrite inferred
update_test_datawrite inferred
delete_test_datadelete inferred
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.