# JFSecure (mcpb · jfs-2.6.3.mcpb)

Let AI agents use secrets without seeing them: masked output, every use approved in JFSecure.

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- mcpb · `jfs-2.6.3.mcpb`: 37/100 (this document), [markdown](https://verifymcp.io/servers/theone55-jfs/jfs.md), [page](https://verifymcp.io/servers/theone55-jfs/jfs)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theone55/jfs/releases/download/v2.6.3/jfs-2.6.3.mcpb`
- Transport: `stdio`
- SHA-256: `e8b25b92089832c11f6744c3f5ad9196be6b08a93ea2a353d6689a36a0a84d99`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 0/100
  - 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 could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 870 tokens (~290/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 2 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.

## Install

### How do I install the JFSecure MCP server?

JFSecure 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, e8b25b92089832c11f6744c3f5ad9196be6b08a93ea2a353d6689a36a0a84d99; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/theone55/jfs/releases/download/v2.6.3/jfs-2.6.3.mcpb`
- SHA-256: `e8b25b92089832c11f6744c3f5ad9196be6b08a93ea2a353d6689a36a0a84d99`

### Verify on macOS / Linux

```bash
echo "e8b25b92089832c11f6744c3f5ad9196be6b08a93ea2a353d6689a36a0a84d99  jfs-2.6.3.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\jfs-2.6.3.mcpb).Hash -eq "e8b25b92089832c11f6744c3f5ad9196be6b08a93ea2a353d6689a36a0a84d99"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 37, +28)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 91

### 2026-10-13 (score 9, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-12 (score 9)

First indexed and scored.

## MCP tools (3)

### `list_secrets` (~91 tokens)

Names only (never values): every secret (folder/name), 2FA code and SSH key (name + fingerprint) of the vault open in JFSecure; or one secret's keys, each with the environment variable it becomes in run_with_secrets; or the secrets in a folder.

Input parameters:

- `path` (string): optional: a secret ("work/github") to list its keys, or a folder

### `run_with_secrets` (~488 tokens)

Run a command with the $key:value lines of a JFSecure secret as environment variables (named like the key in upper case: $db-password → DB_PASSWORD, $token → TOKEN; list_secrets shows them) — all of them, or only `keys`. Not needed for ssh / git with a JFSecure SSH key: run those directly. The user approves it in JFSecure, seeing the exact command. The command is NOT run by a shell (on Windows a .cmd / .bat such as npm runs as that file, its arguments quoted for cmd): to use a variable in an argument start a shell yourself, e.g. ["bash", "-c", "curl -s -H \"Authorization: Bearer $TOKEN\" https://api.github.com/user"] (Windows: ["powershell", "-NoProfile", "-Command", "... $env:TOKEN ..."]). stdout / stderr come back with every value replaced by [JFSecure: NAME] — best-effort masking of the exact values, not a guarantee; don't try to print, transform or exfiltrate values. A user's "Allow 15 min" covers re-running exactly this command (also if a script it runs has changed) — nothing else. Calls run one at a time; there is no cancelling one (timeout_seconds bounds it).

Input parameters:

- `answers` (object): answers to {{?question}} templates in the values
- `command` (array, required): the program and its arguments
- `cwd` (string): working directory (default: this server's)
- `keys` (array): optional: only these keys (or variable names) become variables — pass the ones the command needs (required for a secret of a shared vault)
- `secret` (string, required): the secret's name, with its folder if the name is used twice ("work/github")
- `stdin` (string): optional: a key of the secret (or its variable name) whose value is written to the command's stdin — exactly the value, no new line added. For programs that read a password from stdin (docker login -…
- `timeout_seconds` (integer): at the timeout the command and everything it started are killed; a command that ends in time may leave a background process (a server) running

### `render_template` (~142 tokens)

Write a file from a template, filling in {{Secret:key}}, {{folder/Secret:key}} and {{totp:Name}} from JFSecure (anything else in {{ }} stays as written). The user approves it, seeing the names and the output path. You get the names filled in, never the content — don't read the written file back into the conversation. Use absolute paths.

Input parameters:

- `answers` (object)
- `output` (string, required): path of the file to write, e.g. /project/.env (only the user can read it)
- `template` (string, required): path of the template file, e.g. /project/.env.tpl

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/theone55-jfs/jfs#diagnostics

## Score history

- 2026-10-18: 37
- 2026-10-17: 37
- 2026-10-16: 37
- 2026-10-15: 37
- 2026-10-14: 9
- 2026-10-13: 9
- 2026-10-12: 9

## Common questions

### What is the JFSecure MCP server?

JFSecure is an MCP server listed in the public MCP registry as io.github.theone55/jfs. Let AI agents use secrets without seeing them: masked output, every use approved in JFSecure. This page covers its MCPB bundle (https://github.com/theone55/jfs/releases/download/v2.6.3/jfs-2.6.3.mcpb).

### Is the JFSecure MCP server safe to use?

JFSecure scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the JFSecure MCP server expose?

JFSecure exposes 3 tools: list_secrets, run_with_secrets, render_template. Their descriptions and schemas cost roughly 721 tokens of context every time the server is loaded.

### What licence is the JFSecure MCP server under?

JFSecure declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theone55/jfs
- Website: https://secure.jfolio.org/agents
- Changelog RSS feed: https://verifymcp.io/servers/theone55-jfs/jfs.xml
- Changelog JSON feed: https://verifymcp.io/servers/theone55-jfs/jfs.json
- HTML version of this page: https://verifymcp.io/servers/theone55-jfs/jfs