docket (yielab/docket) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

C
Emerging
74/100
10 days ago

docket

Python CLI ops/control plane for OpenClaw agent fleets — pod provisioning, runtime isolation, governance gates, and budget guardrails.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

yielab

Source: github_code

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 →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: CONTEXT_BYTES_PER_TOKEN, DOCKET_SERVE_TOKEN, DOCKET_LLM_API_KEY
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.
configUV_CACHE_DIR
configDOCKET_RUNTIME_BUILD_TMPDIR
configDOCKET_HOMEState lives under ~/.docket/ by default ( relocates it). Docket-owned JSON writes are
configSITES_DIR
configDOCKET_LOG_DIR
configTRACES_DIR
configAUDIT_LOG_MAX_BYTES
configPOLICIES_DIR
configAPPROVALS_DIR
configSCHEDULE_FILE
configRUNS_FILE
configSESSION_TIMEOUT
configAPPROVAL_TIMEOUT
configTOOL_APPROVAL_TIMEOUT
configTOOL_APPROVAL_POLL_INTERVAL_S
configCLAIM_STALE_TIMEOUT
configMETRICS_WINDOW
configRUNAWAY_TURNS_THRESHOLD
configRUNAWAY_COST_THRESHOLD
configDOCKET_KEY_MAX_AGE_DAYS
configTRACE_RETENTION_DAYS
🔐 secretCONTEXT_BYTES_PER_TOKEN
configCONTEXT_TOKEN_BUDGET
configDISTILL_TIMEOUT_S
configDISTILL_MAX_INPUT_BYTES
configDISPATCH_RETRIES_DEFAULT
configDISPATCH_RETRY_BACKOFF_S
configSESSIONS_DIR
configAGENT_LOOP_MAX_ITERATIONS
configAGENT_LOOP_MAX_TOOL_CALLS
configAGENT_LOOP_MAX_CONSECUTIVE_TOOL_DENIALS
configDOCKET_TOOL_MAX_OUTPUT_CHARS
configAGENT_LOOP_WALL_CLOCK_TIMEOUT_S
configAGENT_LOOP_TOKEN_BUDGET
configAGENT_LOOP_REQUEST_TIMEOUT_S
configMCP_SERVERS_FILE
configMCP_CLIENT_TIMEOUT_S
configMCP_CLIENT_MAX_TIMEOUT_S
configFETCH_ALLOWED_DOMAINS
configFETCH_MAX_RESPONSE_BYTES
configFETCH_TIMEOUT_S
configFLEET_FILE
configTELEGRAM_POLL_TIMEOUT_S
configTELEGRAM_REQUEST_TIMEOUT_S
configDOCKET_SECRETS_BACKEND
configDOCKET_KEYRING_SERVICE
configDOCKET_NO_TRACE
configDOCKET_SANDBOX_IMAGE
🔐 secretDOCKET_SERVE_TOKEN
configEDITOR
configVISUAL
configDOCKET_LLM_BASE_URL
🔐 secretDOCKET_LLM_API_KEY
configDOCKET_SANDBOX_BACKEND
// 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

18/18 tools missing one or more hints — dynamic_tool_323 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_pods (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.

Secrets not logged

1 secret value sent to print

Redact or omit secret values from log output.

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 3 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/yielab/docket)](https://m8ven.ai/mcp/yielab/docket)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: eab5a606ed23d6a6d47d336028e43203edd3b770
code hash: 7ea573ef004162a0d85ea7b9200f2e7a4e91579db06fabc2e0943185a0ec883c
verified: 9/2/2026, 10:55:48 AM
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