io.github.privacyplaybook/sops-mcp

MCPcommunity
v0.10.0io.github.privacyplaybookUnknownUpdated 2mo agoGitHub

MCP server for creating and managing SOPS-encrypted secrets

MCP server for creating and managing SOPS-encrypted secret files using age encryption. Designed for Claude Code (or any MCP client) to produce encrypted files without the model ever seeing plaintext values. All file content is passed as text parameters and returned as text — the server has no filesystem access to the client. Two goals drive the design: 1. Keep secrets in your source tree without…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.privacyplaybook
LicenseUnknown
Version0.10.0
Sourcemcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/25
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/10
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
CVE scan · clean+30/30
Static analysis · clean+20/20
npm provenance (Sigstore)+0/5
Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface
Security scan✓ Cleanv0.10.0 · 19d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

MCP server for creating and managing SOPS-encrypted secret files using age encryption. Designed for Claude Code (or any MCP client) to produce encrypted files without the model ever seeing plaintext values. All file content is passed as text parameters and returned as text — the server has no filesystem access to the client. Two goals drive the design: 1. Keep secrets in your source tree without leaking them. For a small project, running a full secrets manager (Vault, AWS Secrets Manager, etc.)…

Keywords
mcp