hush
NPM · @OMAREI/HUSH · SCANNED OCT 1
Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to omarei-omoto/hush). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1462 tokens (~162/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the hush MCP server?
hush runs locally as an npm package, launched with npx -y @omarei/hush. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @omarei/hush
claude mcp add omarei-omoto-hush -- npx -y @omarei/hush
{
"mcpServers": {
"omarei-omoto-hush": {
"command": "npx",
"args": [
"-y",
"@omarei/hush"
]
}
}
} {
"servers": {
"omarei-omoto-hush": {
"command": "npx",
"args": [
"-y",
"@omarei/hush"
]
}
}
} codex mcp add omarei-omoto-hush -- npx -y @omarei/hush
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"omarei-omoto-hush": {
"type": "local",
"command": [
"npx",
"-y",
"@omarei/hush"
],
"enabled": true
}
}
} openclaw mcp add omarei-omoto-hush --command npx --arg -y --arg @omarei/hush
mcp_servers:
omarei-omoto-hush:
command: "npx"
args: ["-y", "@omarei/hush"] {
"McpServers": {
"omarei-omoto-hush": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@omarei/hush"
]
}
}
} assistant mcp add omarei-omoto-hush -t stdio -c npx -a -y @omarei/hush
{
"mcpServers": {
"omarei-omoto-hush": {
"command": "npx",
"args": [
"-y",
"@omarei/hush"
]
}
}
} 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.
- 1 Oct 26 +16
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.9.0 → 0.10.0 functional
- 30 Sept 26 65
First indexed and scored.
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 1 Oct 2026 · Analysed npm/@omarei/hush@0.10.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | omarei-omoto/hush |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/omarei-omoto/hush/.github/workflows/release.yml@refs/tags/v0.10.0 |
| Rekor log index | 3031512963 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4ff428dace36ad843b7537e5a0188b5b6bad8ecc45bcf1eccb0a5aad9e6e28be7f83a9513e811b7fa8ba438d1c043df19d54ce00c0a60ef82e88af123 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
hush_add_secret ~278
Add a credential to the vault WITHOUT it passing through this conversation. A secure input box opens on the user's screen; they paste the value there and it is encrypted straight into the vault. You get back only a confirmation. ALWAYS use this instead of asking the user to paste a key into the chat. Give a set name (created if it doesn't already exist) and either a known service (hush knows which variables it needs, e.g. 'fal') or a bare key.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Deprecated (removed in hush 2.0), used with service — together they mean set "service/account". |
| env | string | – | Deprecated alias for "set", removed in hush 2.0. |
| key | string | – | A single variable name, if this isn't a known service. |
| service | string | – | Deprecated alias (removed in hush 2.0): e.g. 'fal'. hush knows which variables it needs. |
| set | string | – | The set to add this to, e.g. 'work-fal'. Created if absent. Default: the project's default set. |
| where | string | – | Where to create a new set: this project's vault (default) or the user's own library. |
| why | string | – | Shown to the user so they know what they are approving. |
No output schema declared.
No examples provided.
hush_check_repo ~73
Scan the current codebase for the environment variables it references, and report which are present in the vault and which are missing. Use this before running or building a project to find out whether its configuration is complete.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | – |
| path | string | – | Directory to scan (default: project root). |
No output schema declared.
No examples provided.
hush_describe_secret ~78
Describe one secret without revealing it: whether it exists, its length, a masked preview, who last set it and when. Use this to confirm a credential is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Deprecated alias for "set", removed in hush 2.0. |
| key | string | yes | – |
| set | string | – | – |
No output schema declared.
No examples provided.
hush_list_accounts ~46
Deprecated (removed in hush 2.0), use hush_list_sets — this returns exactly the same thing. Kept registered so a skill file written before sets replaced accounts still works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hush_list_secrets ~95
List the NAMES of secrets available in one named set of the current project's vault. Returns names, which set they live in, and when they were last changed. Never returns secret values — use hush_run to actually use a secret.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | Deprecated alias for "set", removed in hush 2.0. |
| set | string | – | Which set to list (default: the project's default set). |
No output schema declared.
No examples provided.
hush_list_sets ~113
List every named set the agent could use with this project: sets in the user's own library (global, e.g. 'Personal fal', 'Work fal') and sets in the project's own vault. Each entry says where it lives (library or project), whether this project already uses it, and its key names. Call this when the user names a set loosely ("use my acme fal key", "the work fal account") so you can pass the right name to hush_run. Returns names only, never values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hush_provision ~165
Prepare a CLI or codebase to run with the right credentials. Give it a tool name (e.g. 'wrangler') and optionally which set to use. It works out which service the tool authenticates with, checks which of this project's used sets already provide it, prompts the user to add it if missing, and tells you the exact hush_run call to make. Use this when the user says something like 'set up wrangler with my personal Cloudflare set'.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | Override the detected service. |
| set | string | – | Which set to check, e.g. 'work-fal'. Default: whichever of this project's used sets already provide it. |
| tool | string | yes | The command that needs credentials, e.g. 'wrangler'. |
No output schema declared.
No examples provided.
hush_request ~312
Make an authenticated HTTP request without the credential ever entering this conversation. Write $NAME where a secret belongs and hush substitutes it from the vault inside its own process; you get back the response with any secret values masked as [redacted:NAME]. Use this for any API call that needs a key, instead of trying to run curl/wget (denied) or building an Authorization header yourself. Secrets go into HEADER VALUES only unless you also list 'body' or 'query' in substitute. https only; the host must be one the policy allows.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Request body. Substituted only if "body" is in substitute. |
| headers | object | – | Header name to value. Put the secret placeholder in the value, e.g. {"Authorization": "Bearer $STRIPE_KEY"}. The value is substituted inside hush and never returned to you. |
| method | string | – | HTTP method. Default GET, or POST when a body is given. |
| sets | array | – | Extra named sets to layer on top of this project's usual ones, for this call only, e.g. ["work-stripe"]. Later entries win on a shared key name. Use hush_list_sets to see the options. |
| substitute | array | – | Extra places, besides header values, where $NAME may be replaced. Omit for header values only, which is the safe default. |
| url | string | yes | Full URL, e.g. "https://api.stripe.com/v1/refunds". |
No output schema declared.
No examples provided.
hush_run ~240
Run a shell command with the project's secrets injected as environment variables. The command sees real credentials; you only see its output, with any secret values masked. This is the correct way to perform a task that needs a credential (migrations, deploys, authenticated API calls) without the credential entering this conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | object | – | Deprecated alias for sets (removed in hush 2.0): {"fal":"acme"} means the set named "fal/acme". Prefer sets. |
| args | array | – | Arguments, e.g. ['run','build']. |
| command | string | yes | Executable to run, e.g. 'npm'. |
| cwd | string | – | – |
| env | string | – | Deprecated (removed in hush 2.0): the base set for this run, layered under sets. Prefer sets. |
| sets | array | – | Extra named sets to layer on top of this project's usual ones, for this run only, e.g. ["work-fal"]. Later entries win over earlier ones on a shared key name. Use hush_list_sets to see the options. O… |
No output schema declared.
No examples provided.
What is the hush MCP server?
hush is an MCP server listed in the public MCP registry as io.github.omarei-omoto/hush. Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools. This page covers its npm package (@omarei/hush).
Is the hush MCP server safe to use?
hush scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 hush MCP server expose?
hush exposes 9 tools: hush_list_secrets, hush_list_sets, hush_list_accounts, hush_check_repo, hush_run, and 4 more. Their descriptions and schemas cost roughly 1,400 tokens of context every time the server is loaded.
Is the hush MCP server still maintained?
hush is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the hush MCP server under?
hush declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.