技能潮 SkillTide 提交收录
官方说明3 个来源MCP 服务3 天前
cordum-io/cordum

cordum-io/cordum

🏎️ 🏠 ☁️ - Safety-first agent control plane with pre-dispatch policy evaluation (deny/escalate/allow), output…
在 GitHub 查看 ↗直链 · 无中转页
官方说明🏎️ 🏠 ☁️ - 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
来源明细
收录自 rohitg00/awesome-devops-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-14 · 最近见到 2026-10-16 · 共见到 4 次 · 被 3 个来源列出
评分构成
综合分 303 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-10-14;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

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
来源
awesome · https://github.com/cordum-io/cordum
按领域浏览
MCP 服务
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引