Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
D

draugr-dev/draugr

Independent directory — not the official site. Details below come from the project's public repository.

Describe your app in one file, and Draugr hands back the findings in the order to fix them.

30 ★ measured · checked 2026-11-19

Before you install: no copy-paste command · license Apache-2.0

First step: nothing runnable here yet - start from the repository: https://github.com/draugr-dev/draugr

★ 30·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page

We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →

Star count
30 ★ · draugr-dev/draugr · read from the GitHub search API · (checked 2026-11-19 20:00:48)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 30 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository draugr-dev/draugr;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Draugr

Excerpted from the repository README (abridged)

> Know which security findings to fix first, across the scanners you already run. SAST, SCA, secrets, IaC and containers, every finding ranked by exposure, criticality, exploitability and, for Go, reachability.
Describe your app in one file, and Draugr hands back the findings in the order to fix them.
Every application carries problems nobody put there on purpose: a library that turned out to have a
hole in it, a password committed by accident, a server setting that leaves a door open. Draugr finds
them, works out which ones actually matter for your app, and answers the question you are really
asking before a release, is this safe to ship?
It runs the established open-source scanners for you, Trivy, Semgrep, Gitleaks and others, so there
is nothing to choose between, wire up, or read five of. You describe what you built, once, in one
file: where the repositories are, what images it builds, what it exposes, what infrastructure it
runs on. Draugr picks the checks that apply, runs the right tool for each, and produces evidence you
can hand to somebody else. Bring the scanners you already pay for, or use the open-source defaults.
Findings are ranked, not listed. A scanner's "critical" describes a flaw in the abstract,
how bad it could be at its worst, anywhere. The same flaw is act-now in the service strangers can
reach and backlog in the internal tool three people use, and no scanner can tell those apart because
the difference is in the file you wrote, not in the code. And draugr diff
gates a pull request on new findings only, so inheriting two hundred existing ones does not
block every change.
Quickstart · See it in action ·
What it checks · In your pipeline ·
Documentation · What Draugr doesn't promise ·
Security
## See it in action
Priority (P1–P4) is not severity. Severity says how bad a flaw is at its worst, anywhere.
Priority weighs that against how exposed and how important the part of your app it sits in is, which
no scanner can work out, because it is not in the code.
draugr-dev/draugr-demo is a deliberately
vulnerable app wired to Draugr: every control lights up, findings land in the repo's
Security → Code scanning tab, and its example pull requests show the new-vs-fixed diff.
## Quickstart
bash
curl -fsSL https://draugr.dev/install.sh | sh
Installs to ~/.local/bin, no sudo, and installs nothing if the archive fails
verification. The script is readable in the
repo; a download by hand, the GitHub CLI and go install are in the install
guide.
bash
draugr tools install # fetch the scanners a scan here runs, pinned and verified
draugr scan . # scan this repository, no descriptor needed
tools install reads the tree as draugr init does, or the descriptor beside it, so a small service
gets the few scanners it runs rather than every one Draugr can provision. --all when you are
preparing a machine for several projects.
Then describe what you actually ship, with draugr init writing a first draft:
yaml
project: my-app
release:
version: "1.0"
config:
controls:
images:
enabled: true
components:
name: web
images:
image: alpine:3.19
bash
draugr scan draugr.saga.yaml # console summary; exits non-zero on fail
draugr scan draugr.saga.yaml -o out/ # also writes report.json + results.sarif
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/draugr-dev-draugr/)
Source
awesome · https://github.com/draugr-dev/draugr
Browse by field
MCP servers
Traction
30 ★
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index