Serveur MCP SafeGrd
Commit 8 nov. 2026Automatise les sauvegardes chiffrées et les tests d'intégrité pour les bases de données, les arborescences de répertoires et les boîtes mail IMAP avec verrouillage d'objets compatible S3.
Aussi connu sous safegrd/cli, cli
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.0.29
- Dernier commit
- 8 nov. 2026
- Licence
- —
Qu'est-ce que SafeGrd MCP ?
Automatise les sauvegardes chiffrées et les tests d'intégrité pour les bases de données, les arborescences de répertoires et les boîtes mail IMAP avec verrouillage d'objets compatible S3.
Résumé généré à partir du README du projet
À propos du MCP server SafeGrd
SafeGrd fournit un système automatisé pour la création de sauvegardes chiffrées et la réalisation de tests d'intégrité pour diverses sources de données. Il prend en charge les bases de données PostgreSQL, MySQL, MariaDB, MongoDB et SQLite, ainsi que les arborescences de répertoires et les boîtes mail IMAP. L'outil compresse les données avec zstd et les chiffre à l'aide d'age directement sur l'hôte avant de les envoyer vers un stockage compatible S3 avec Object Lock activé. Cela garantit que les données sont protégées contre la suppression ou la modification par des agents non autorisés.
Les utilisateurs peuvent gérer ces tâches via une CLI ou un démon. Le système permet une gestion flexible des clés, où vous pouvez choisir de conserver les clés de chiffrement localement ou de laisser le serveur distant les conserver dans un état scellé pour les hôtes enregistrés. Pour la vérification, la fonctionnalité Fire Drill restaure les sauvegardes dans des environnements temporaires afin de valider que chaque table, ligne et fichier est intact. Cette configuration est conçue pour les développeurs et les administrateurs système qui ont besoin d'une protection de données fiable et vérifiable pour les environnements de production.
Ce que vous pouvez faire avec
- 1Vérifier l'intégrité des sauvegardesLancez un Fire Drill pour restaurer une sauvegarde dans une base de données temporaire et vérifier que toutes les lignes et tables sont correctes.
- 2Protéger contre les commandes destructricesExécutez une commande dangereuse uniquement après qu'un snapshot verrouillé a été créé avec succès.
- 3Effectuer des sauvegardes de fichiers incrémentiellesSauvegardez une arborescence de répertoires où seuls les blocs modifiés sont téléchargés après l'exécution mensuelle initiale.
- 4Restaurer des fichiers spécifiquesRécupérez une version unique d'un fichier spécifique à partir d'un snapshot précédent sans restaurer l'ensemble du jeu de données.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer SafeGrd MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller SafeGrd MCP dans Claude Code
$ claude mcp add cli -- docker run -i --rm ghcr.io/safegrd/cli:0.0.29Installer SafeGrd MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/safegrd/cli:0.0.29"
]
}
}
}Installer SafeGrd MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/safegrd/cli:0.0.29"
]
}
}
}Installer SafeGrd MCP dans VS Code CLI
$ code --add-mcp '{"name":"cli","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/safegrd/cli:0.0.29"]}'Installer SafeGrd MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/safegrd/cli:0.0.29"
]
}
}
}Installer SafeGrd MCP dans Codex
$ codex mcp add cli -- docker run -i --rm ghcr.io/safegrd/cli:0.0.29Installer SafeGrd MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.cli] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/safegrd/cli:0.0.29"]
Installer SafeGrd MCP dans Gemini CLI
$ gemini mcp add -s user cli docker -- run -i --rm ghcr.io/safegrd/cli:0.0.29Installer SafeGrd MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/safegrd/cli:0.0.29"
]
}
}
}Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessiblesafegrd/cli is public and reachablegithub.com/safegrd/cli ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)No licenseFaille
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-08github.com/safegrd/cli ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPHTTPS endpoint answered 401 (sign-in required)Réussi
README
Voir sur GitHubSafeGrd CLI (safegrd)
safegrd backs up PostgreSQL, MySQL, MariaDB, MongoDB and SQLite databases, directory trees
and IMAP mailboxes. Each backup is compressed with zstd and encrypted with age on the host that
takes it, then written to S3-compatible storage under Object Lock. It is restored on a schedule
to check that every table, row and file came back.
It is the CLI and daemon of SafeGrd. Documentation is at safegrd.dev/docs, and every command and flag is in the command reference.
- Backups go from your host straight to storage. The remote server receives a record of each backup (when it ran, its size, its digest and the date its lock ends) and the signed result of each restore test. The data never passes through it.
- You choose who holds the key. By default the remote server keeps your key sealed and
releases it only to your enrolled hosts, so you can restore even after losing a host. With
enroll --key-custody local, only you can decrypt these backups. - Restores are tested. A Fire Drill restores the newest backup into a throwaway database or directory, compares its tables, rows and digests with what was backed up, and signs the result.
- An agent cannot remove a backup.
safegrd guardtakes a locked snapshot before a destructive command runs, and a personal access token cannot delete a backup or shorten its lock.
Installation
Install script (Linux and macOS)
curl -fsSL https://safegrd.dev/install.sh | sh
It detects your OS and architecture, downloads the matching release archive, checks
it against the release's checksums.txt, and installs safegrd to /usr/local/bin
(or ~/.local/bin when it cannot use sudo). The script is install.sh
in this repository; https://raw.githubusercontent.com/safegrd/cli/main/install.sh
serves the same file.
When it runs in a terminal, it then offers to connect the machine to a remote server:
a browser login, a question about who holds the encryption key, then safegrd enroll.
The login prints a URL and a code that you can open in a browser on any device, so
it works the same on a server you reached over SSH or PuTTY. Without a terminal (CI,
cloud-init, cron) it installs and stops.
Options are environment variables, and they go on the sh after the pipe. Written
before curl they apply to curl, and the script never sees them:
curl -fsSL https://safegrd.dev/install.sh | VERSION=v0.0.3 sh # pin a release
curl -fsSL https://safegrd.dev/install.sh | SAFEGRD_INSTALL_DIR=~/.local/bin sh # no sudo
curl -fsSL https://safegrd.dev/install.sh | SAFEGRD_NO_SETUP=1 sh # install only
| Variable | Effect |
|---|---|
VERSION |
Release tag to install. Default: the latest release. |
SAFEGRD_INSTALL_DIR |
Where the binary goes. |
SAFEGRD_NO_SETUP=1 |
Install only; do not offer to log in and enroll. |
SAFEGRD_FORCE_INSTALL=1 |
Download and install even when the release asked for is already installed. |
SAFEGRD_PROJECT |
Project ID or slug to enroll this machine into. |
SAFEGRD_STORAGE |
hosted or local: where backups go when the project has no bucket. |
SAFEGRD_CLAIM |
The claim code the console shows for this machine. It carries the project, where backups go and the surfaces to protect, so enrollment writes them into the config and asks nothing. Needs a release whose enroll has --claim; an older one stops and says so. |
SAFEGRD_NODE_NAME |
Name the machine is shown under. |
SAFEGRD_KEY_CUSTODY |
local keeps this host's key on the host. Without it the remote server keeps the key sealed and releases it only to your enrolled hosts. |
SAFEGRD_SERVER_URL |
Remote server to log in and enroll with. Default: https://safegrd.dev. |
Homebrew (macOS and Linux)
brew install safegrd/tap/safegrd
The formula installs the same release archives as the script.
Go
go install github.com/safegrd/cli/cmd/safegrd@latest
Container image
ghcr.io/safegrd/cli runs on linux/amd64 and linux/arm64 and carries pg_dump, mysqldump
and mongodump, and a PostgreSQL 18 server so a drill can restore a database into a
throwaway cluster on the volume. The tag names the Postgres client: <version>-pg18 reads
Postgres 18 and every older server. Releases are signed with cosign (keyless, from this repository's release
workflow):
cosign verify ghcr.io/safegrd/cli:<version>-pg18 \
--certificate-identity-regexp 'https://github.com/safegrd/cli/.github/workflows/release.yml@.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
packaging/compose runs the daemon beside a database,
packaging/kubernetes runs daemon run --once as a
CronJob, and packaging/helm/safegrd runs the daemon as a
Deployment.
Each names the release it was cut with, such as ghcr.io/safegrd/cli:0.0.10; change
the tag to upgrade.
Release archives, or from source
Static binaries for Linux and macOS (amd64, arm64) and their SHA-256 checksums are
on the releases page. To build:
git clone https://github.com/safegrd/cli.git && cd cli
make build
Try it before you sign up
With no account, one command backs up a database and restores it to check:
safegrd try postgres://app:secret@db.example.com/app # or env:DATABASE_URL, a MySQL, MongoDB or SQLite URL, or a directory
safegrd signup # keep it: the host, its backup and a daily schedule
The backup is encrypted on this host, stored on the remote server's storage for 24 hours, and restored in memory from there. Details are in the install guide.
Quickstart
1. Create a config and a key
Skip this if you let the install script connect the machine: it already wrote the
keypair and ~/.safegrd/config.yaml, and init refuses to overwrite them.
# writes an age X25519 keypair and ~/.safegrd/config.yaml
safegrd init \
--database-url "postgres://postgres:password@localhost:5432/myapp_prod" \
--storage local \
--local-path ./backups \
--retention-days 14
2. Connect to a remote server (optional)
# Prints a URL and a code: open it in a browser on any device, including over SSH
safegrd login
# Register this machine, generating its encryption key if it has none.
# --key-custody decides whether the server keeps a copy (safegrd) or not (local)
safegrd enroll --key-custody local
# A host that should encrypt but never decrypt: make the key pair on your laptop,
# then put only the printed public key in the host's encryption.public_key
safegrd keygen --out ~/.safegrd/keys/prod.key
# Headless / CI: a Personal Access Token instead of the browser
safegrd enroll --token "sg_pat_..."
# Or with the claim code the console's setup shows: the project, where backups go and
# the surfaces are written into ~/.safegrd/config.yaml, and the key stays on this machine
safegrd enroll --claim <code>
safegrd doctor # every surface opens from this host; the console shows the result
safegrd daemon run --once
# Later, on an enrolled host: add the surfaces named for it in the console
# (Add surface on its row). Only adds; the old config is kept as config.yaml.bak
safegrd claim
safegrd daemon restart
# Verify the active session
safegrd whoami
3. Back up
# dumps, compresses, encrypts with age on this host, and writes to locked storage
safegrd backup
4. Run a Fire Drill
# restores into an empty database and checks every table's row count
safegrd verify \
--snapshot snap-20260919-01 \
--sandbox-target "postgres://postgres:password@localhost:5432/ephemeral_test_db"
5. Restore
safegrd restore \
--snapshot snap-20260919-01 \
--target "postgres://postgres:password@localhost:5432/myapp_recovered"
6. Protect several things on one host, unattended
Each entry under surfaces: in ~/.safegrd/config.yaml is one protected thing, and
safegrd daemon install runs them on their schedules. A surface's credential block says
where its secret comes from; the config never holds it:
surfaces:
- id: app-primary
type: postgres
schedule: "@daily"
credential:
from: env # or: command (with run), file (with path),
name: APP_DATABASE_URL # or safegrd: the remote server holds it for this host
- id: user-uploads
type: files
schedule: "6h"
roots: ["/var/www/uploads"]
safegrd.example.yaml is the annotated version. The daemon reads its
config when it starts, so run safegrd daemon restart after changing it.
7. Take a locked snapshot before a destructive command
safegrd guard backs up one surface, waits until the snapshot is uploaded and locked, and
then runs the command. If the backup fails or the snapshot is not locked, the command does
not run and guard exits 3.
safegrd guard --surface app-primary -- psql "$APP_DATABASE_URL" -c 'DROP TABLE sessions'
safegrd guard -- terraform destroy
# The commands a hook treats as destructive, and a check that takes no backup
safegrd guard --list
safegrd guard --matches "npx prisma migrate reset" # exit 0: it matches
Storage on the host's own disk, or a bucket with worm_mode: NONE, cannot lock a snapshot,
so guard refuses there unless you pass --allow-unlocked.
A locked snapshot of the surface younger than --max-age stands in for a new backup, so an
agent running several destructive commands in a row backs up once. --check-only takes no
backup at all and refuses the command unless such a snapshot exists:
safegrd guard --max-age 30m -- psql "$APP_DATABASE_URL" -c 'TRUNCATE sessions'
safegrd guard --max-age 1h --check-only -- terraform destroy
safegrd list --json prints every snapshot with its lock date, for scripts.
8. Back up a directory tree, and get one file back
File backups are incremental: the first run of each month uploads every file, and every run after it uploads only the chunks that changed. Every kept version of every file is searchable, and one file restores on its own.
safegrd backup --files /srv/app --exclude '*.tmp,node_modules/*'
# every kept version of a file, numbered from the oldest
safegrd find etc/nginx/nginx.conf
# one version of one file, or a directory as it was in one snapshot
safegrd restore --path etc/nginx/nginx.conf --version 2 --target-dir ./out
safegrd restore --snapshot snap-20260919-01 --path 'var/www/**' --target-dir ./out
# every pack present and every listing consistent, without restoring anything
safegrd check --all
# a bucket over the S3 API (Supabase Storage, or any S3-compatible store)
safegrd backup --files s3://avatars --source-endpoint https://PROJECT.storage.supabase.co/storage/v1/s3 \
--source-region eu-central-1 --source-access-key env:S3_KEY --source-secret-key env:S3_SECRET
# and back into the bucket, each object with the content type it had
safegrd restore --snapshot snap-20261012-01 --target s3://avatars --source-endpoint https://PROJECT.storage.supabase.co/storage/v1/s3 \
--source-region eu-central-1 --source-access-key env:S3_KEY --source-secret-key env:S3_SECRET
--format tar keeps one archive per backup instead. What is locked, for how long, and
what a restore brings back: safegrd.dev/docs/surfaces/files.
AI agents (MCP)
safegrd has two MCP servers. Neither has a tool that deletes a backup, changes where
backups go, or takes a private key.
The local server, safegrd mcp, runs on a host over stdio and uses that host's config
and key. Its tools are status, list, doctor, backup, verify, restore and
export, each running the command of the same name. restore writes only into a new or
empty directory or an empty database.
claude mcp add safegrd-local -- safegrd mcp
# a host that runs the container image: mount the volume it enrolled with
claude mcp add safegrd-local -- docker run -i --rm \
-v safegrd:/home/safegrd/.safegrd ghcr.io/safegrd/cli mcp
The remote server, https://safegrd.dev/mcp, reads every host's backups and Fire Drills
and asks for a backup or a drill now, on every plan. Add it with no header, then run /mcp
in Claude Code and choose Authenticate: you sign in to SafeGrd in the browser and approve.
claude mcp add --transport http safegrd https://safegrd.dev/mcp
The Claude Code plugin in safegrd/agent-plugins adds the same server, signed in the same way, with skills that back up and run a Fire Drill before a risky change:
/plugin marketplace add safegrd/agent-plugins
/plugin install safegrd@safegrd
A client that cannot sign in, such as CI, sends a personal access token from the console's
Tokens page as Authorization: Bearer sg_pat_....
Both servers are listed in the MCP Registry
as dev.safegrd/safegrd, and the remote one on Smithery.
Cursor and VS Code configs, and every tool's arguments: safegrd.dev/docs/mcp.
What it backs up
- PostgreSQL, incrementally: the schema comes from
pg_dumpand the rows stream over binaryCOPYfrom the same snapshot, so arrays, enums, foreign keys, views, triggers and sequence positions all come back. Each run uploads only the chunks of each table that changed,restore --tableloads chosen tables into a running database, and--change-logskips reading tables nothing wrote since the last run.--format tarkeeps one archive per backup. Needs apg_dumpat least as new as the server on the host. - SQLite, incrementally: copied through SQLite's online backup in one read transaction, so transactions still in the WAL are in it and writers carry on. The copy keeps the database's pages in place, so each run uploads only the chunks whose pages changed.
--format tarkeeps one archive per backup. Needs nothing installed on the host. - MySQL and MariaDB through
mysqldump --single-transaction, and MongoDB throughmongodump --archive, one archive per backup. - Directory trees, incrementally: each run uploads only the chunks that changed, every object is locked once when it is written, and
safegrd findlists every kept version of a file forrestore --path --version. - IMAP mailboxes, every message as RFC 5322 mail, checked by SHA-256 on every drill.
- Locked storage: S3 Object Lock in compliance mode, or governance mode where a lock may need lifting. Storage on the host's own disk, and a bucket with
worm_mode: NONE, keep backups without a lock. - Fire Drills: restore backups on a schedule, count what came back, and sign a record of each test.
Development
Go 1.25 or newer. make with no target lists everything.
make build # compile bin/safegrd
make test # unit and integration tests, race detector
make ci # the exact gate CI runs: gofmt check, tidy check, vet, race tests
make dist # cross-compile release archives + checksums into dist/
make fmt tidy # the developer-facing fixers (these rewrite files; `ci` never does)
CI runs make ci on every push and pull request, so a green local run means a
green pipeline. Tagging v* runs make dist VERSION=<tag without v> and
publishes the archives and checksums.txt as a GitHub Release.
License
Business Source License 1.1, with an Additional Use Grant. See LICENSE.
In short: read, modify and build it freely, and use it for evaluation anywhere. Production use is included with a SafeGrd account on any plan, the free one too. Listing, verifying, restoring and exporting your backups is always permitted, with or without an account. Each version becomes GPL-3.0-or-later four years after it is published. For a commercial license, contact support@safegrd.dev.
Questions sur SafeGrd MCP
Comment ajouter SafeGrd MCP à Claude Code ?
Exécutez claude mcp add cli -- docker run -i --rm ghcr.io/safegrd/cli:0.0.29 dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter SafeGrd MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Un agent peut-il supprimer une sauvegarde ?
Non, le système est conçu de manière à ce qu'un agent ou un jeton d'accès personnel ne puisse ni supprimer une sauvegarde, ni réduire sa durée de verrouillage.
Comment les sauvegardes sont-elles sécurisées ?
Les sauvegardes sont compressées avec zstd et chiffrées avec age sur l'hôte avant d'être écrites sur un stockage compatible S3 avec l'option Object Lock activée.
Qu'est-ce qu'un Fire Drill ?
Un Fire Drill est un test de restauration qui restaure la sauvegarde la plus récente dans un environnement éphémère afin de vérifier que toutes les tables, lignes et fichiers sont intacts.
Le serveur distant voit-il mes données ?
Non, les données sont chiffrées sur votre hôte et envoyées directement au stockage ; le serveur distant ne reçoit que les métadonnées et les résultats des tests de restauration.