ZERO MCP
PYPI · ZERO-ENGINE · SCANNED SEP 20
Read-only MCP inspection for ZERO paper autonomous onchain operations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 80 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 822 tokens (~19/item across 42 items; 20 tools + 22 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ZERO MCP server?
ZERO MCP runs locally as a PyPI package, launched with uvx zero-engine. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · zero-engine
claude mcp add zero-intel-zero -- uvx zero-engine
{
"mcpServers": {
"zero-intel-zero": {
"command": "uvx",
"args": [
"zero-engine"
]
}
}
} {
"servers": {
"zero-intel-zero": {
"command": "uvx",
"args": [
"zero-engine"
]
}
}
} codex mcp add zero-intel-zero -- uvx zero-engine
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zero-intel-zero": {
"type": "local",
"command": [
"uvx",
"zero-engine"
],
"enabled": true
}
}
} openclaw mcp add zero-intel-zero --command uvx --arg zero-engine
mcp_servers:
zero-intel-zero:
command: "uvx"
args: ["zero-engine"] {
"McpServers": {
"zero-intel-zero": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"zero-engine"
]
}
}
} assistant mcp add zero-intel-zero -t stdio -c uvx -a zero-engine
{
"mcpServers": {
"zero-intel-zero": {
"command": "uvx",
"args": [
"zero-engine"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 14 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/zero-engine@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
zero_get_backtest_report ~24
Read-only deterministic paper backtest report without PnL claims.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_decision_stack ~24
Read-only paper-only lens, layer, and modifier decision stack.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_evidence_bundle ~23
Read-only hash-only evidence bundle from the bundled paper runtime.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_evolve_status ~19
Read-only paper-first evolve gate status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_genesis_proposals ~20
Read-only plan-only genesis proposal classifications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_health ~21
Read-only paper runtime health, dependency, and breaker status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_immune_status ~23
Read-only paper immune breaker and risk-allowance status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_journal_tail ~22
Read-only paper decision journal tail from the bundled scenario.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_memory_snapshot ~22
Read-only public-safe local memory snapshot from bundled paper decisions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_memory_stats ~19
Read-only aggregate memory stats without entry bodies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_network_proof_pack ~22
Read-only public-safe ZERO Network proof-chain manifest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_paper_results ~21
Read-only replay of the deterministic bundled paper scenario.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_position_state ~21
Read-only paper position state derived from the bundled scenario.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_proof_pack ~20
Read-only public-safe demo proof-pack manifest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_rejection_audit ~23
Read-only paper rejection audit grouped by stage and reason.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_research_report ~20
Read-only paper-only research command-chain report.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_runtime_parity ~25
Read-only production-parity OODA report with disabled live shadow execution.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_runtime_status ~21
Read-only paper runtime status derived from the bundled scenario.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_get_safety_catalog ~21
Read-only MCP safety catalog for every public tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zero_list_strategies ~22
Read-only list of bundled paper strategies and contributor examples.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ZERO MCP server?
ZERO MCP is listed in the public MCP registry as io.github.zero-intel/zero. Read-only MCP inspection for ZERO paper autonomous onchain operations. This page covers its PyPI package (zero-engine).
Is the ZERO MCP server safe to use?
ZERO MCP scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ZERO MCP server expose?
ZERO MCP exposes 20 tools: zero_list_strategies, zero_get_runtime_status, zero_get_runtime_parity, zero_get_health, zero_get_paper_results, and 15 more. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.
Is the ZERO MCP server still maintained?
ZERO MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.