Mmcp.market

hush MCP server

by royashbrook.com·com.royashbrook/hush·v1.3.0

A secret store for AI agents: the agent never sees the plaintext.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

20 stars

Reviews

Write one

Nobody has reviewed hush yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

hush tools (1)

write = sends, deletes, buys or posts
  • get_skillFree

    Get the full SKILL.md playbook for hush so you can install + use it.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 272ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the hush repository's README, as published. We do not edit it. Read it on GitHub

a secret store for AI agents, the one with no get.

get a secret once into the OS keychain, then inject it into commands forever, the value never hits stdout, the transcript, or the cloud.

A secret store for AI agents, with one hard rule: the agent never sees the plaintext.

Values never reach stdout, so they never land in the tool result, the transcript, or the cloud. A secret only ever moves from the store straight into the consumer. There's no get on purpose, a plain getter is the leak.

The point: you (an agent) are running as the user with their CLIs already authed, so you can already set a server-side secret or call a service, you just can't see the value without it landing in the chat. hush gets it once into the OS keychain, then you inject it into those commands forever. No chat paste, no temp files, no .env to commit by accident.

agents: start here

If you were handed this repo's url, install yourself, then follow the playbook. Get the hush script onto the box and read SKILL.md, that's the whole onboarding (it covers store / mint / inject and how to adopt hush in the repo you're working in). The script is one self-contained bash file; put it wherever your agent loads tools or just on your PATH:

git clone https://github.com/royashbrook/hush
chmod +x hush/hush
# then put hush/hush on your PATH, or move it into your agent's skills/tools dir

or run it straight from npm without cloning: npx @royashbrook/hush (mac/linux; on windows use the clone, the orchestrator is bash).

Claude Code convenience (auto-loads as a skill): clone straight into the skills dir instead, whole session git clone https://github.com/royashbrook/hush ~/.claude/skills/hush, or one project ./.claude/skills/hush. Other agents: see AGENTS.md.

That's it, the human points you here and says "use the hush skill," and you take it from here. The one thing only a human can do is paste a secret they hold: when you hit that, run hush set and a hidden dialog pops on their screen (you never see the value).

install (humans)

Same clone as above, or just grab the single hush script and put it on your PATH.

Backends: macOS Keychain, Linux libsecret (secret-tool), and Windows DPAPI (via PowerShell) are built in. On other platforms keep the same contract with your OS secret store (see SKILL.md). Cross-OS tested in CI (manual workflow_dispatch, all three runners).

maintenance (opt-in)

hush doctor checks local installation drift and backup health without opening the secret store. hush doctor --check-updates explicitly checks the public npm version. daily notices, agent-readable status, and reversible scheduler repair are covered in maintenance without surprises. nothing auto-upgrades.

quick start

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

claude mcp add --transport http hush https://royashbrook.com/hush
Add to Cursor

hush: common questions

Is hush MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the hush safety report
How do I install hush?
It runs remotely at royashbrook.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does hush need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is hush maintained?
The last commit was 3 days ago (2026-09-24). The latest release is v1.3.0.
Is hush up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of hush?
Servers from other publishers that do the same job: Delx Memory MCP server, Apify MCP server and Heimdall MCP server. Compare all hush alternatives.

Alternatives to hush

Same job from other publishers: the closest match first, then the best rated.

All hush alternatives →
  • Delx Memory
    Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
    A
  • Apify
    Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
    A
  • Heimdall
    Every App Store Connect + StoreKit 2 endpoint. 890 tools in 13 profiles, narrow to 27.
    B
  • Buywhere
    Agent-native product catalog: 300M+ products, 150,000+ stores, deliver_to ranking.
    A
  • Workflows
    Store, query, and create YAML workflow playbooks for LLM agents.
    A

More from royashbrook.com →