LeashIndex Get the report

Index / other

gecko-mcp

io-github-frumane-gecko-mcp declares 41 capabilities across 41 tools, with 2 critical issues.

93/100 exposureHigh exposure

Manifest recorded 2026-10-12 from tools/list answered by the npm package gecko-mcp@2.2.4 (published to npm as gecko-mcp, listed in the official MCP registry as io.github.Frumane/gecko-mcp 2.2.4), run in an isolated container with no network access and no 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 41 tools

41 of 41 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 · 6 of 41 tools

6 tools are classified as irreversible and declare no limit.

high · no-expiry · All 41 tools

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

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

20 tools can modify data and declare no limit.

low · uncapped-read · 15 of 41 tools

15 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_tabsread declared
open_tabwrite assumed
get_active_tabread declared
navigate_tabdestructive declared
close_tabdestructive declared
read_pageread declared
screenshotread declared
findread declared
clickwrite assumed
snapshotread declared
type_textwrite assumed
fill_formwrite assumed
press_keywrite assumed
wait_for_elementread declared
get_valueread declared
real_typewrite assumed
real_keywrite assumed
real_cleardelete inferred
hoverwrite assumed
double_clickwrite assumed
right_clickwrite assumed
select_optionwrite assumed
set_checkedwrite inferred
submit_formdestructive declared
upload_filedestructive declared
get_attributeread declared
get_articleread declared
get_cookiesread declared
wait_for_network_idleread declared
list_workspacesread declared
switch_workspaceread inferred
window_boundsread declared
move_cursorwrite inferred
real_clickwrite assumed
enable_os_inputwrite assumed
disable_os_inputwrite assumed
evaluatedestructive declared
enable_evaluatewrite assumed
disable_evaluatewrite assumed
launch_floorpwrite assumed
launchwrite 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.