LeashIndex Get the report

Index / storage

Browsentic

io-github-imshaikot-browsentic declares 52 capabilities across 52 tools, with 2 critical issues.

94/100 exposureHigh exposure

Manifest recorded 2026-10-22 from tools/list answered by the npm package browsentic@0.9.0 (published to npm as browsentic, listed in the official MCP registry as io.github.imshaikot/browsentic 0.9.0), 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 52 tools

52 of 52 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 · 3 of 52 tools

3 tools are classified as irreversible and declare no limit.

high · no-expiry · All 52 tools

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

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

30 tools can modify data and declare no limit.

low · uncapped-read · 19 of 52 tools

19 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
page_getPageInforead inferred
page_scrollTowrite assumed
page_clickElementwrite assumed
page_trustedClickwrite assumed
page_findCaptcharead inferred
page_solveCaptcharead inferred
page_hoverElementwrite assumed
page_dragElementwrite assumed
page_focusInputwrite assumed
page_fillInputwrite assumed
page_typeTextwrite assumed
page_selectOptionwrite assumed
page_selectTextwrite assumed
page_extractTextread inferred
page_pickElementwrite assumed
page_pressKeysend inferred
page_submitFormwrite assumed
page_waitForElementwrite assumed
page_listSiteToolsread inferred
page_callSiteToolwrite assumed
page_findProgressread inferred
page_findSearchread inferred
page_readThemeread inferred
page_auditContrastwrite assumed
page_applyThemewrite assumed
page_startDiagnosticsread inferred
page_readConsoleread inferred
page_readNetworkread inferred
page_stopDiagnosticswrite assumed
page_startMonitorwrite assumed
page_monitorStatusread inferred
page_awaitMonitorwrite assumed
page_stopMonitorwrite assumed
page_startTimerwrite assumed
page_timerStatusread inferred
page_stopTimerdelete inferred
page_highlightElementwrite assumed
page_searchSiteread inferred
page_navigatewrite assumed
page_openTabwrite assumed
page_switchTabwrite assumed
page_switchFramewrite assumed
page_closeTabdelete inferred
page_screenshotwrite assumed
page_listFilesread inferred
page_attachFilewrite assumed
page_captureDownloadwrite assumed
page_listDownloadsread inferred
page_listRecordingsread inferred
page_readRecordingread inferred
browsentic_statusread inferred
browsentic_openSkillwrite 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.