Dedicated Homebrew tap distributing codesigned Locksmith binaries, MCP server, and CyberArk Summon provider with macOS biometric entitlements.
MCPpedia last refreshed this data
Homebrew Locksmith is an MCP server that dedicated Homebrew tap distributing codesigned Locksmith binaries, MCP server, and CyberArk Summon provider with macOS biometric entitlements. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 70/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"homebrew-locksmith": {
"url": "<see-readme-for-url>"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This tap has migrated to bonjoski/tap > Locksmith is now distributed alongside the entire Bonjoski sovereign AI agent security fabric (Fabrial, Aegisbox, Airlock, Argus, Shield, Conjoiner, and Locksmith) in the unified tap. > brew untap bonjoski/locksmith > brew install bonjoski/tap/locksmith
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in security / analytics
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP server for 1Password service accounts — tools and resources for vaults and credentials
Ask your agent about your own Apple Health data: 194 metrics, 22 tools, local, 0 deps.
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
MCP Security Weekly
Get CVE alerts and security updates for Homebrew Locksmith and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
[!IMPORTANT] This tap has migrated to
bonjoski/tap
Locksmith is now distributed alongside the entire Bonjoski sovereign AI agent security fabric (Fabrial, Aegisbox, Airlock, Argus, Shield, Conjoiner, and Locksmith) in the unified tap.brew untap bonjoski/locksmith brew tap bonjoski/tap brew install bonjoski/tap/locksmith
The official Homebrew Tap for Locksmith — a secure, biometric-protected keychain vault for macOS.
This tap distributes:
locksmith: The primary CLI and Model Context Protocol (MCP) server.summon-locksmith: The official Summon provider, allowing seamless biometric-gated secrets injection into your development and DevOps processes.[!TIP] Why use Homebrew?
Installing via Homebrew is the recommended distribution method for macOS. It downloads pre-built, cryptographically signed binaries compiled in a hardened environment, ensuring maximum compatibility with macOS security policies (Touch ID access, sandboxing, and Keychain access group restrictions).
Tap the repository and install the formula:
# Tap the repository
brew tap bonjoski/locksmith
# Install Locksmith & its Summon provider
brew install locksmith
If your local Git configuration enforces SSH connections globally, you might encounter a Permission denied (publickey) or authentication prompt when tapping. You can bypass this temporary restriction for the install command:
GIT_CONFIG_GLOBAL=/dev/null brew tap bonjoski/locksmith
Ensure both the core CLI and the Summon provider are installed correctly and match the active version:
# Verify the core Locksmith CLI
locksmith --version
# Verify the Summon Provider extension
summon-locksmith --version
Both should return the active version (e.g., v${VERSION}).
Here's how to quickly get started with Locksmith on macOS:
Add a secret to your secure macOS Keychain. By default, secrets are biometric-protected:
locksmith add my-service my-secret-value --expires 30d
This will trigger a native Touch ID/Apple Watch prompt on your Mac before retrieving the secret:
locksmith get my-service
Use the bundled summon-locksmith provider to run commands with environment variables resolved straight from the keychain:
Create a secrets.yml file:
API_KEY: !var my-service
Execute a process securely (Touch ID will prompt to unlock the environment variables):
summon --provider locksmith -f secrets.yml env | grep API_KEY
Each binary distributed through this tap is cryptographically signed and includes a SLSA level 2 attestation. You can verify the integrity of the binary locally:
# Install the GitHub CLI if you haven't already
brew install gh
# Verify the attestation directly against the release
gh attestation verify $(which locksmith) --repo bonjoski/locksmith
For more detailed configuration, MCP server setup, and advanced settings, visit the main Locksmith Repository.
Contributions to this formula or issues regarding the