Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-zero-intel-zero": {
"args": [
"zero-engine"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Autonomous operating system for self-custodial onchain operations: open ZERO Runtime, Protocol, and Proof.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'zero-engine' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked zero-engine against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
MCP server for Spanning Cloud Backup — M365/GWS/Salesforce backups, restores, audit.
AI agent control of 3D printers — 432 tools for OctoPrint, Moonraker, Bambu, Prusa, Elegoo
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
MCP Security Weekly
Get CVE alerts and security updates for io.github.zero-intel/zero and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Autonomous operating system for self-custodial onchain operations: open ZERO Runtime, Protocol, and Proof.
This repository is the open Runtime, Protocol, and Proof substrate for ZERO. The hosted product surfaces live at getzero.dev, app.getzero.dev, and the public developer entrypoint at getzero.dev/developers. This repo stays focused on runnable software: paper-first execution, safety gates, local journals, Hyperliquid read-only/live boundaries, MCP-compatible readouts, public proof packets, and verification contracts.
Not another trading bot. ZERO is Runtime plus Proof for autonomous onchain operations that must stay inspectable, interruptible, and self-custodial.
The first proof is intentionally simple: the runtime boots in paper mode, live
risk refuses closed, public proof packets verify, and no custody is required.
The live proof bridge is separate: a redacted zero.live_trading_evidence.v1
packet proves operator-owned Hyperliquid live execution evidence exists without
publishing raw venue records, wallet addresses, or private journals.
Run the same checks locally with:
just paper-api-smoke
just public-proof
ZERO's public Railway template is live: Dockerfile build, railway.toml,
/health, durable /data journal volume, Railway doctor, redacted deployment
evidence packs, and paper-mode live-risk refusal.
Live public paper demo: https://zero-production-5214.up.railway.app
Railway template: https://railway.com/deploy/zero-paper-runtime
Use docs/railway-template.md as the marketplace configuration source of truth. The current Railway Template Publish Packet is tracked in contracts/distribution/railway-template.json. The Railway partner submission packet is tracked in docs/railway-partner.md.
scripts/railway_doctor.py https://zero-production-5214.up.railway.app
ZERO has three non-negotiable product rules:
ZERO's first-run path is local, paper-first, and does not need exchange credentials:
git clone https://github.com/zero-intel/zero.git
cd zero
just bootstrap
just paper-api
In another terminal:
cd zero/cli
cargo run -q -p zero-os -- --api http://127.0.0.1:8765
Inside the terminal, press Ctrl+5 or run /cockpit-mode for the read-only
Runtime control packet. The command name is legacy CLI language; public product
copy should call the surface ZERO Control. In paper/default mode it should
refuse live risk and show the reason:
runtime control
live_mode=refused ready=false risk_allowed=false controls_ready=false
next: fix preflight check live_executor: live executor not configured
operator: handle=local-operator role=owner scope=local-private
preflight: passed=2/10 failed=8
immune: open=2 risk_blocking=2
reconciliation: not_configured risk_allowed=false
receipts: total=0 accepted=0 refused=0 exchange_error=0
actions: re
... [View full README on GitHub](https://github.com/zero-intel/zero#readme)