Convert Office files, images and e-books to PDF; merge, compress or protect local PDFs.
ShieldFive is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Tidy your E2E-encrypted ShieldFive vault and local folders. Decrypts locally; revocable access.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user shieldfive-mcp '--' npx -y @shieldfive/mcp
# 2 — ask your agent for something these tools do
# list_local, find_duplicates, find_large_files and 16 more
ShieldFive costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts ShieldFive as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user shieldfive-mcp '--' npx -y @shieldfive/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take SHIELDFIVE_GRANT, SHIELDFIVE_MCP_ROOTS if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List files in an allowed local directory, with sizes and modification dates.
No parameter schema on file.
Find files with byte-identical contents. Identity is decided by a full SHA-256
No parameter schema on file.
List files at or above a size threshold, largest first.
No parameter schema on file.
List files not modified for a given number of days. Modification time is a weak
No parameter schema on file.
Total file count and bytes for the allowed roots, broken down by file extension
No parameter schema on file.
Move a file, directory or symlink to another location inside the allowed roots.
No parameter schema on file.
Rename an item in place; a symlink is renamed itself. new_name must be a bare
No parameter schema on file.
Create a directory (and any missing parents) inside the allowed roots.
No parameter schema on file.
Move files or folders into a .shieldfive-mcp-trash directory inside their own
No parameter schema on file.
List files in the ShieldFive vault folders this connection covers, with decrypted names, paths,
No parameter schema on file.
Search the vault by name, path, file type, size or date. Runs locally over names decrypted in
No parameter schema on file.
Total usage in this connection’s scope, the biggest folders and files, and a breakdown by file type.
No parameter schema on file.
Find byte-identical files in the vault. Same-size files are downloaded, decrypted in memory and
No parameter schema on file.
Decrypt a text file in memory and return its contents inside an <untrusted-file-content> block.
No parameter schema on file.
Rename a file or folder. Needs the
No parameter schema on file.
Move a file or folder into another folder this connection covers. Needs
No parameter schema on file.
Create a folder inside one this connection covers. Needs
No parameter schema on file.
Move up to ${VAULT_LIMITS.trashItems} files or folders into this connection’s folder in the owner’s
No parameter schema on file.
Connect this assistant to the user’s ShieldFive vault. Opens ShieldFive in the user’s browser, where
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ShieldFive or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.6.6. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ShieldFive can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.