SkillTide Submit
Official description3 sourcesMCP servers3d ago
cordum-io/cordum

cordum-io/cordum

๐ŸŽ๏ธ ๐Ÿ  โ˜๏ธ - Safety-first agent control plane with pre-dispatch policy evaluation (deny/escalate/allow), outputโ€ฆ
View on GitHub โ†—Direct link ยท no redirect page
Official description๐ŸŽ๏ธ ๐Ÿ  โ˜๏ธ - Safety-first agent control plane with pre-dispatch policy evaluation (deny/escalate/allow), output scanning (PII, secrets, injection), job scheduling, and full audit trail. Native MCP server
Source
collected from the rohitg00/awesome-devops-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-14 ยท last seen 2026-10-16 ยท seen 4ร— ยท listed by 3 sources
Score
score 303 ยท 3 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆœๅŠก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-14๏ผ›last seen 2026-10-16ใ€‚There is no official certification or quality rating here โ€” we record sources and dates only.
Third-party quality signals

Cordum

ไปฅไธ‹ๆ‘˜ๅฝ•่‡ช่ฏฅไป“ๅบ“็š„ README๏ผˆ็‰‡ๆฎต๏ผ‰ ยท ๅœจ GitHub ่ฏปๅฎŒๆ•ด README โ†’

Know What Your AI Agents Are Doing. Before They Do It.
The Source-Available Agent Control Plane for Governance, Safety, and Trust.
Includes Cordum Edge โ€” a Compliance Firewall for Claude Code and other local AI-agent actions.
Discord ยท Discussions ยท Docs
---
Quickstart
First Time?
| Goal | Path |
|------|------|
| **Just want to try it?** | ./tools/scripts/quickstart.sh โ€” one-command install from source (Option A below) |
| **Run the full stack from pre-built images?** | docker compose pull && docker compose up -d (Option B below) |
| **Developing Cordum?** | See Development |
Option A: Install from source
One command stands up the full stack โ€” API gateway, scheduler, safety
kernel, workflow engine, context engine, dashboard, NATS, and
TLS-secured Redis โ€” with auto-generated secrets, auto-provisioned
certificates, and a post-deploy smoke test that exercises a real
approval workflow:
**Prerequisites:** Docker Desktop v4+ (or Engine v20.10+ with Compose v2,
โ‰ฅ 4 GB RAM allocated), Go 1.26.3+ (for first-run cert generation), and
curl. On Windows use MSYS2 / Git Bash / WSL.
**What you get at the end:**
- Dashboard at http://localhost:8082 โ€” log in as admin / ChangeMe123!
(the default dev password, also saved to .env as CORDUM_ADMIN_PASSWORD;
change it before exposing the stack).
- Gateway at http://localhost:8081 with a generated CORDUM_API_KEY in
.env.
- TLS CA, server, and client keypairs under ./certs/.
- A working approval-gate workflow proven by the built-in
platform_smoke.sh run.
Full walkthrough, platform notes, and troubleshooting:
docs/quickstart.md.
Option B: Run the published images
**Prerequisites:** Docker Desktop v4+ or Docker Engine v20.10+ with the
Compose v2 plugin (โ‰ฅ 4 GB RAM allocated), jq (recommended, for parsing
API responses), and Go 1.26.3+ (for one-time local cert generation โ€”
docker compose mounts ./certs but does not create it).
**Dashboard:** http://localhost:8082
**Login:** this path leaves user auth off by default โ€” sign in on the dashboard
with your CORDUM_API_KEY. To enable admin password login instead, set
CORDUM_USER_AUTH_ENABLED=true and a policy-compliant CORDUM_ADMIN_PASSWORD
(โ‰ฅ 12 chars, with an uppercase letter, a digit, and a special character) in
.env, then docker compose up -d. (The quickstart script in Option A does
this for you.)
Pin a specific release by exporting CORDUM_VERSION=1.2.3 before
docker compose pull. Defaults to :latest, which only moves on stable
release tags (pre-release suffixes such as -rc.1 never promote
:latest).
Verifying image signatures
Every release-tag image is signed with [cosign] keyless OIDC. The example
below verifies api-gateway; repeat the same command (swapping the image
name) for each of the seven Cordum images before deploying to production โ€”
verifying one image does not attest the rest:
See docs/deployment/images.md for the full
image catalogue, a verify-all-images snippet, multi-arch pull instructions,
and tag policy.
[cosign]: https://docs.sigstore.dev/cosign/overview/
Manual setup (without docker compose)
Deploy to Kubernetes
--set values land in the Helm release's stored values (and your shell
history) โ€” fine for a quick eval, but for production prefer
redis.auth.existingSecret (see cordum-helm/values.yaml) over
redis.auth.password, and patch secrets.apiKey into the rendered
Secret out-of-band rather than passing it on the command line; that
chart doesn't yet have an existingSecret equivalent for the API key.
See cordum-helm/ for the full Helm chart reference. The
chart is also available on Artifact Hub.
**Container images** (multi-arch: linux/amd64 + linux/arm64):
| Image | GHCR | Docker Hub |
|-------|------|------------|
| api-gateway | ghcr.io/cordum-io/cordum/api-gateway | cordum/api-gateway |
| scheduler | ghcr.io/cordum-io/cordum/scheduler | cordum/scheduler |
| safety-kernel | ghcr.io/cordum-io/cordum/safety-kernel | cordum/safety-kernel |
| workflow-engine | ghcr.io/cordum-io/cordum/workflow-engine | cordum/workflow-engine |
| context-engine | ghcr.io/cordum-io/cordum/context-engine | cordum/context-engine |
| mcp | ghcr.io/cordum-io/cordum/mcp | cordum/mcp |
| dashboard | ghcr.io/cordum-io/cordum/dashboard | cordum/dashboard |
Full catalogue, tag policy, cosign verification recipe, and multi-arch
Source
awesome ยท https://github.com/cordum-io/cordum
Browse by field
MCP servers
added
yesterday

More in MCP servers

All 5,525 in MCP servers โ†’

Filed under

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

Browse all fields โ†’

โ† Back to index