Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Universal File Opener CLI

MCPB · LINUX-X64

Inspect files, extract content and make guarded edits locally. Linux x86_64, glibc 2.35+.

Available components

mcpb · linux-x64 5
0 this week 5 Trust /100

Last scanned (17 hours ago)

Scores higher than 9% of MCPB servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.Unverified
Provenance & Transparency26
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance not yet verified. View diagnostics → Unverified
  • License not yet determined.Unverified
  • Maintenance history not yet determined.Unverified
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • Source repository
  • Security disclosure

Checks we could not complete (12)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this bundle is larger than we will inspect (50 MiB to download, 100,000 files or 256 MiB unpacked), so we did not read it. This is a limit on our side, not a finding about the bundle.
  • Provenance in Provenance & TransparencyBuild provenance not yet verified.
  • License in Provenance & TransparencyLicense not yet determined.
  • Maintenance in Provenance & TransparencyMaintenance history not yet determined.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 0
    • Package version: 1.10.2 → 4.0.0 functional
  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 25 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 24 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 20 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
    • Package version: 1.10.1 → 1.10.2 functional
  • 18 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 15 Oct 26 0
    • Package version: 1.7.1 → 1.10.1 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Analysed mcpb/https://github.com/krauqllc/ufo-cli/releases/download/v4.0.0/ufo-cli-4.0.0-linux-x64.mcpb@4.0.0

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem mcpb
Reason Package details unavailable

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Universal File Opener CLI MCP server?

Universal File Opener CLI ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, da9a109aaf2ed449d4f05ab1a6b66f368908258772da02d2c80de95cdb425402; the commands to do that are on this page. If it does not match, do not open it.

mcpb · linux-x64

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

da9a109aaf2ed449d4f05ab1a6b66f368908258772da02d2c80de95cdb425402

macOS / Linux 

echo "da9a109aaf2ed449d4f05ab1a6b66f368908258772da02d2c80de95cdb425402  ufo-cli-4.0.0-linux-x64.mcpb" | shasum -a 256 -c

Windows (PowerShell) 

(Get-FileHash -Algorithm SHA256 .\ufo-cli-4.0.0-linux-x64.mcpb).Hash -eq "da9a109aaf2ed449d4f05ab1a6b66f368908258772da02d2c80de95cdb425402"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.