Covenant Guard MCP server
org.opencovenant/guard·v0.1.1·8 starsHard spend cap, OS sandbox, and signed receipts for unattended coding agents like Claude Code.
8 stars
Reviews
Write oneNobody has reviewed Covenant Guard yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Covenant Guard tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
How Covenant Guard compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,243 servers
- GitHub stars
- 8
- more than 86% of 28,706 servers
Install Covenant Guard in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Covenant Guard repository's README, as published. We do not edit it. Read it on GitHub
Covenant
Open infrastructure for agent-native computing.
Covenant sits below agent applications and above the host operating system. It owns the state, authority, and accountability concerns that recur across agent frameworks — scoped capabilities, durable memory, runtime isolation, append-only audit, and commit-scoped provenance — so individual frameworks can stop reinventing them.
<!-- METRICS:START --> Status. Local control plane is real and live-tested (50 Rust crates, ~284k lines, 3870 source-discovered Rust tests including 486 live boundary tests). Production-grade sandboxing for hostile agent code and networked multi-peer operation are roadmap; the Solana settlement program is deployed on mainnet (credits, staking, slashing, on-chain receipt anchoring), but its daemon-driven economic lifecycle is not yet production. See BUILT.md for the explicit honesty boundary. <!-- METRICS:END -->
Multi-chain reach. The trust layer also projects onto Base mainnet as signed statements any EVM contract verifies with one ecrecover — ERC-8004 agent registration, a deployed bond-receipt verifier, a registered EAS reputation schema, and an ENS CCIP-Read gateway (*.agents.opencovenant.eth) — while $CVNT stays a single Solana mint that is never bridged or wrapped and every per-call fee and bond is chain-local USDC. On-chain reputation writes and funded USDC bonds are registered but not yet exercised, while live x402 sellers settle chain-local USDC on both Solana and Base mainnet, and on Robinhood Chain mainnet (chain 4663) a USDG x402 payment and an on-chain bounded-spend escrow are proven with real USDG. See docs/multichain-value-capture.md.
- Web: opencovenant.org
- Docs: docs.opencovenant.org
- Paper: DOI: 10.5281/zenodo.20134416
- Token: $CVNT · 2mNVZ6aEjrGwiUVCfz7XGWpiXuWzgBDoznwE579upump
Quick start
Try it without installing — sandbox.opencovenant.org. Public operator console wired to a live daemon, state resets every 12 hours.
To run it locally, build the daemon and CLI, register the sample agent, and start the daemon:
git clone https://github.com/open-covenant/covenant && cd covenant
cd agent-os && cargo build --workspace --exclude covenant-settlement-program --locked
# Register the example agent (daemon loads $COVENANT_HOME/agents/ at startup)
mkdir -p ~/.covenant/agents
cp -R ../examples/hello-agent ~/.covenant/agents/hello
# Start the daemon
./target/debug/covenantdThen drive it from either surface — they share the same daemon, audit chain, and capability store.
CLI
./target/debug/covenant capabilities grant memory.write
./target/debug/covenant capabilities grant intent.subscribe
./target/debug/covenant intent "say hello"Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Covenant Guard: common questions
- Is Covenant Guard MCP server safe?
- Mostly: it is graded B (83/100). Read the Covenant Guard safety report
- Does Covenant Guard need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Covenant Guard maintained?
- The last commit was 40 days ago (2026-09-26). The latest release is v0.1.1.
- What can I use instead of Covenant Guard?
- Servers from other publishers that do the same job: Nautilus Compass Memory MCP server.
- How does Covenant Guard compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,243 servers); github stars 8 (more than 86% of 28,706 servers). Full comparison.
Alternatives to Covenant Guard
Same job from other publishers: the closest match first, then the best rated.
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB