cli-agent-orchestrator (awslabs/cli-agent-orchestrator) is an MCP server listed on the M8ven Trust Index. It scores 98 out of 100, grade A. It declares 38 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
A
Trusted
98/100
8 days ago

cli-agent-orchestrator

Multi-agent orchestration for AI coding CLIs — Claude Code, Kiro, Codex, and more, coordinated in isolated tmux sessions

→ awslabs/cli-agent-orchestrator· listed on github_topic

Trusted. Deep verification, no outstanding findings, and an established reputation. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

awslabs

Source: github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: CAO_ELASTIC_RELEASE_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: CAO_ELASTIC_BROKER_TOKEN, CAO_ELASTIC_RELEASE_TOKEN, CAO_AUTH_LOCAL_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configE2E_PORT
configCAO_ENABLE_WORKING_DIRECTORY
configCAO_TERMINAL_ID
configCAO_ELASTIC_BROKER_URL
🔐 secretCAO_ELASTIC_BROKER_TOKEN
configCAO_ELASTIC_WORKER_READY_WAIT
configCAO_ELASTIC_WORKER_ID
🔐 secretCAO_ELASTIC_RELEASE_TOKEN
configCAO_WORKFLOW_RUN_ID
configCAO_WORKFLOW_STEP_ID
configCAO_AUTH_AUDIENCE
configAUTH0_AUDIENCE
configCAO_AGUI_ENABLED
configCAO_AGENTS_DIR
configARCHFLAGS
configCAO_HOME_DIR
configCAO_PYTE_STATUS
configCAO_EAGER_INBOX_DELIVERY
configCAO_GRAPH_EXPORT_ROOT
configCAO_API_HOST
configCAO_API_PORT
configXDG_CONFIG_HOME
configCAO_TMP_DIR
configGROK_HOME
configCAO_HERMES_IDLE_LOG_REGEX
configCAO_HERMES_USER_PREFIX_REGEX
configCAO_HERMES_MAX_STABLE_IDLE_POLLS
configMINIMAX_DATA_DIR
configAUTH0_DOMAIN
configCAO_AUTH_JWKS_URI
configCAO_AUTH_ISSUER
🔐 secretCAO_AUTH_LOCAL_TOKEN
configCAO_PROFILE_ALLOWED_HOSTS
configCAO_MEMORY_API_URL
configCAO_PROJECT_ID
configCAO_MAX_TERMINALS
configCAO_MEMORY_ENABLED
configCAO_MEMORY_LEARNING_ENABLED
configCAO_MEMORY_INSTRUCTION_PROMOTION_ENABLED
configCAO_MEMORY_FLUSH_THRESHOLD
configCAO_MEMORY_LINT_ENABLED
configCAO_WORKFLOW_REQUIRE_APPROVAL
configCAO_MEMORY_COMPILE_MODE
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

42/42 tools missing one or more hints — handoff (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); handoff (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); assign (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +39 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/awslabs/cli-agent-orchestrator)](https://m8ven.ai/mcp/awslabs/cli-agent-orchestrator)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c0c9b723222dc85a1ac8f751dc3daf71e5dbcd76
code hash: 7da601a2a18d9c2716f01595d2da81a2e4dcc5ea3ebb46edfc7c12a69872f507
verified: 9/2/2026, 4:44:16 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client