LeashIndex Get the report

Index / devtools

okffs

io-github-neturely-okffs declares 24 capabilities across 24 tools, with 2 critical issues. 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.

82/100 exposureHigh exposure

Manifest recorded 2026-11-04 from tools/list answered by the npm package @neturely/okffs@0.15.0 (published to npm as @neturely/okffs, listed in the official MCP registry as io.github.neturely/okffs 0.15.0), 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 24 tools

24 of 24 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 · 4 of 24 tools

4 tools are classified as irreversible and declare no limit.

high · no-expiry · All 24 tools

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

24 of 24 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 · 14 of 24 tools

14 tools can modify data and declare no limit.

low · uncapped-read · 6 of 24 tools

6 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
create_issuewrite inferred
list_issuesread inferred
close_issuedelete inferred
delete_issuedelete inferred
delete_branchdelete inferred
get_issueread inferred
comment_issuesend inferred
create_issues_from_listread inferred
planwrite inferred
link_issueswrite inferred
create_pull_requestwrite inferred
commit_and_updatewrite inferred
list_pr_review_commentsread inferred
reply_to_review_commentwrite assumed
resolve_review_threadwrite assumed
prepare_releasewrite assumed
update_project_statusread inferred
set_issue_fieldswrite inferred
update_issuewrite inferred
promote_branchwrite inferred
merge_pull_requestwrite inferred
fix_into_basewrite assumed
get_pr_checksread inferred
configurewrite assumed

Record history

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

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