Zeus Dev Helper
PYPI · ZEUS-DEV-HELPER-MCP · SCANNED SEP 21
Coach first Zeus Client app to green (stdio MCP).
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 hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BSD License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1307 tokens (~72/item across 18 items; 12 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.6.0 and 0.7.3: 33 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Zeus Dev Helper MCP server?
Zeus Dev Helper runs locally as a PyPI package, launched with uvx zeus-dev-helper-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · zeus-dev-helper-mcp
claude mcp add koten-ai-zeus-dev-helper -- uvx zeus-dev-helper-mcp
{
"mcpServers": {
"koten-ai-zeus-dev-helper": {
"command": "uvx",
"args": [
"zeus-dev-helper-mcp"
]
}
}
} {
"servers": {
"koten-ai-zeus-dev-helper": {
"command": "uvx",
"args": [
"zeus-dev-helper-mcp"
]
}
}
} codex mcp add koten-ai-zeus-dev-helper -- uvx zeus-dev-helper-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"koten-ai-zeus-dev-helper": {
"type": "local",
"command": [
"uvx",
"zeus-dev-helper-mcp"
],
"enabled": true
}
}
} openclaw mcp add koten-ai-zeus-dev-helper --command uvx --arg zeus-dev-helper-mcp
mcp_servers:
koten-ai-zeus-dev-helper:
command: "uvx"
args: ["zeus-dev-helper-mcp"] {
"McpServers": {
"koten-ai-zeus-dev-helper": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"zeus-dev-helper-mcp"
]
}
}
} assistant mcp add koten-ai-zeus-dev-helper -t stdio -c uvx -a zeus-dev-helper-mcp
{
"mcpServers": {
"koten-ai-zeus-dev-helper": {
"command": "uvx",
"args": [
"zeus-dev-helper-mcp"
]
}
}
} 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.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Licence: Proprietary → BSD License functional
- Package version: 0.7.1 → 0.7.3 functional
- 17 Sept 26 +20
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- Schema quality: 58 → 72 ▼ functional
- Security disclosure: unverified → fail ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.7.0 → 0.7.1 functional
- 16 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 0
- Stability: 0.17 → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 46 → 58 ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Package version: 0.6.1 → 0.7.0 functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +14
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
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 21 Sept 2026 · Analysed pypi/zeus-dev-helper-mcp@0.7.3
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
bind_contract ~62
Extract stamped contract.hash only. Refuse placeholders / compute_local (ZDH-22).
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | – |
| json_text | string | – | – |
| mode | string | – | – |
| path | string | – | – |
| scope | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
diagnose_error ~131
Map error signals to failure_class + errors.md anchor (ZDH-7 / ZDH-19). Includes Detective URL templates when req_id/chat_id are present (folded detective_links). Does not scrape Hub.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| chat_id | string | – | – |
| error_class | string | – | – |
| error_code | string | – | – |
| message | string | – | – |
| req_id | string | – | – |
| session_id | string | – | – |
| status | string | – | – |
| turn_id | string | – | – |
| zeus_url | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
doctor ~56
Health / doctor. detail: health | env | compat | cache | all. env/compat/cache fold validate_env, compat_check, and semantic_cache_status (those names stay on the lint toolset).
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
next_step ~21
Return the single current checklist blocker + recommended Helper tools (coach).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
readiness_check ~51
Live Zeus platform gates: healthz/readyz/version, auth, bootstrap, chat_request. Never returns secret values. Emits failure_class + next_action on red paths.
| Name | Type | Req | Description |
|---|---|---|---|
| update_checklist | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_surface ~49
Pick Direct vs agent surface + Trace-Class (ZDH-18). Does not call Zeus.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | – |
| needs_llm | – | – | – |
| qps | number | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
scaffold_app ~92
Write a ZeusRuntime middle-man. app_kind=cli (default) or api (FastAPI POST /turn). coding_language=python only today. UI demos use use_sample / demo_travel_sample, not this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| app_kind | string | – | – |
| coding_language | string | – | – |
| force | boolean | – | – |
| project_name | string | – | – |
| target_dir | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_prereq ~128
Store non-secret prereqs for readiness (does not store password/token values). Put real secrets in environment variables (ZEUS_PASSWORD, ZEUS_BEARER_TOKEN, LLM_API_KEY).
| Name | Type | Req | Description |
|---|---|---|---|
| auth_mode | string | – | – |
| bucket | string | – | – |
| collection | string | – | – |
| has_bearer | – | – | – |
| has_llm_key | – | – | – |
| has_password | – | – | – |
| has_username | – | – | – |
| mode | string | – | – |
| role | string | – | – |
| scope | string | – | – |
| zeus_url | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
smoke_test_agent ~76
One ZeusRuntime run_turn (requires kotenai-zeus-client>=2.3.0 + LLM key). If the client is missing and demo_travel_sample documents Docker install, returns guide-only docker compose next_action instead of only pip install.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | – |
| update_checklist | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
smoke_test_zeus ~39
Smoke Zeus without LLM: readiness + POST /v2/{bucket}/{scope}/describe.
| Name | Type | Req | Description |
|---|---|---|---|
| update_checklist | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
start_project ~131
Start or reset first-app coaching checklist (single-agent default). sample: - travel (default) — UI path via demo_travel_sample / use_sample - api — API-only FastAPI scaffold (scaffold_app app_kind=api) - yelp / multi — gated until single-agent smokes green unless force_multi Multi-agent goals (goal=multi or sample=yelp) are gated until single-agent smokes are green, unless force_multi=true (ZDH-11).
| Name | Type | Req | Description |
|---|---|---|---|
| force_multi | boolean | – | – |
| goal | string | – | – |
| sample | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
use_sample ~96
UI sample: locate or clone public demo_travel_sample; set DEMO_TRAVEL_SAMPLE_DIR. project_name = clone directory name (default demo_travel_sample). Extra travel-only phases stay on travel_golden_path (travel toolset).
| Name | Type | Req | Description |
|---|---|---|---|
| clone_if_missing | boolean | – | – |
| parent_dir | string | – | – |
| project_name | string | – | – |
| sample | string | – | – |
| sample_dir | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Zeus Dev Helper MCP server?
Zeus Dev Helper is an MCP server listed in the public MCP registry as io.github.koten-ai/zeus-dev-helper. Coach first Zeus Client app to green (stdio MCP). This page covers its PyPI package (zeus-dev-helper-mcp).
Is the Zeus Dev Helper MCP server safe to use?
Zeus Dev Helper scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Zeus Dev Helper MCP server expose?
Zeus Dev Helper exposes 12 tools: doctor, start_project, next_step, set_prereq, readiness_check, and 7 more. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.
Is the Zeus Dev Helper MCP server still maintained?
Zeus Dev Helper is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.