MCP.Market

SafeGrd MCP server

online · 100% uptime
by safegrd.dev·dev.safegrd/safegrd·v0.0.29
No reviews yet

Read backups and Fire Drills, and ask for a backup or a drill. No tool deletes a backup.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed SafeGrd yet.

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

SafeGrd tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • Live reliabilityremote reachable in 196ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (bearer)9/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SafeGrd compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
47 ms
faster than 93% of 30,031 servers

Install SafeGrd in Claude Code, Cursor or VS Code

claude mcp add --transport http safegrd https://safegrd.dev/mcp
Add to Cursor

What the publisher says

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

SafeGrd 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, written to S3-compatible storage under Object Lock, and 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.

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.

  • Backups go from your host straight to storage. The remote server receives a record of each

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.

  • You choose who holds the key. By default the remote server keeps your key sealed and

directory, compares its tables, rows and digests with what was backed up, and signs the result.

  • Restores are tested. A Fire Drill restores the newest backup into a throwaway database or

destructive command runs, and a personal access token cannot delete a backup or shorten its lock.

  • An agent cannot remove a backup. safegrd guard takes a locked snapshot before a

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

Shortened. The full README is on GitHub.

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

SafeGrd: common questions

Is SafeGrd MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the SafeGrd safety report
How do I install SafeGrd?
It runs remotely at safegrd.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does SafeGrd need an API key?
Yes. The registry entry asks for Authorization.
Is SafeGrd maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.0.29.
Is SafeGrd up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does SafeGrd compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 47 ms (faster than 93% of 30,031 servers). Full comparison.