B+

npm:vaultbox

https://www.npmjs.com/package/vaultbox
89/100 · MCP Trust Grade · checked 1h ago · MCP 0.1.1

What it offers — 4 tools · Commerce

lockbox_init

Initialize lockbox in a project. Creates .vaultbox-key, .secrets/ directory, and updates .gitignore.

lockbox_set

Set (encrypt and store) a secret in the lockbox.

lockbox_list

List secret names (not values) stored in the lockbox.

lockbox_get

Get (decrypt) a secret from the lockbox.

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%92
Tool hygiene15%70
Transparency / provenance15%90

Findings

INFO Static analysis of npm package vaultbox@0.1.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:vaultbox on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:vaultbox grade B+
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B+ · wmcp.sh
[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/npm%3Avaultbox/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Avaultbox)
<a href="https://wmcp.sh/mcp/grade/npm%3Avaultbox"><img src="https://wmcp.sh/mcp/grade/npm%3Avaultbox/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.