LeashIndex Get the report

Index / devtools

Swipium

io-github-geropalombo-swipium declares 55 capabilities across 55 tools, with 2 critical issues.

96/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list answered by the npm package swipium@2.3.5 (published to npm as swipium, listed in the official MCP registry as io.github.GeroPalombo/swipium 2.3.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 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.

critical · irreversible-uncapped · 5 of 55 tools

5 tools are classified as irreversible and declare no limit.

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 · 29 of 55 tools

29 tools can modify data and declare no limit.

low · uncapped-read · 21 of 55 tools

21 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
qa_doctorread declared
qa_start_sessionwrite assumed
qa_prepare_targetwrite assumed
qa_iosdestructive declared
qa_wdawrite inferred
qa_device_inforead declared
qa_orientationwrite inferred
qa_geolocationwrite assumed
qa_networkwrite assumed
qa_metrowrite assumed
qa_app_controldestructive declared
qa_screen_recordread inferred
qa_screenshotwrite assumed
qa_snapshotread declared
qa_inspectread declared
qa_actwrite assumed
qa_clear_overlaywrite assumed
qa_check_healthread declared
qa_job_statusread declared
qa_job_canceldelete inferred
qa_get_artifactread declared
qa_notewrite assumed
qa_visualwrite assumed
qa_flow_checkread declared
qa_flow_runwrite assumed
qa_generatewrite assumed
qa_smokewrite assumed
qa_reportwrite assumed
qa_test_thiswrite assumed
qa_prepare_ios_targetwrite assumed
qa_flow_compilewrite assumed
qa_explorewrite assumed
qa_first_runread inferred
qa_statusread declared
qa_explain_blockerread declared
qa_continue_from_blockerwrite assumed
qa_app_map_buildwrite inferred
qa_app_map_readread declared
qa_app_map_queryread declared
qa_app_map_feature_scoperead declared
qa_app_map_updatedestructive declared
qa_issue_logread inferred
qa_mobile_auditwrite assumed
qa_suite_readread declared
qa_suite_updatedestructive declared
qa_suite_generatewrite assumed
qa_suite_exportwrite assumed
qa_suite_lintread declared
qa_flow_repairwrite assumed
qa_test_featurewrite assumed
qa_resolve_artifactread declared
qa_resolve_targetread declared
qa_buildwrite assumed
qa_bundletoolwrite assumed
qa_waitread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-1396 tools/list answered by the npm package swipium@2.3.0 (published to npm as swipium, listed in the official MCP registry as io.github.GeroPalombo/swipium 2.3.0), run in an isolated container with no network access and placeholder credentials
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.