cladding
For an organization to trust AI with its code, three things must hold — trust, traceability, and stability at scale. cladding wraps your AI coding agent: your intent goes in before it writes, and the result is verified against your spec after, so those three are earned, not assumed. First L4 implementation of the Ironclad standard.
Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
qwerfunch
Source: github_repo_search
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.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
clad_prepare_initclad_stage_initclad_initclad_prepare_clarifyclad_clarifyclad_resolve_onboarding_reviewclad_list_featuresclad_get_featureclad_run_checkRuns `clad check` drift detection. Returns a TERSE report by default (pass, error/warn counts, top 3 blocking findings) to keep the agent loop cheap; pass verbose:true for every finding incl. info-severity + suggestions.
clad_run_gateclad_verdictclad_get_contextclad_get_working_setclad_get_impactclad_get_graphclad_changelogclad_get_eventsReads .cladding/events.log and returns the most recent entries.
clad_prepare_spec_editReturns a projection revision and the canonical input revisions required for one typed operation batch; it never writes.
clad_edit_specclad_beginStarts a feature cycle through feature.begin, saving its one pre-cycle checkpoint and derived inventory together.
clad_create_featureclad_resolve_design_impactclad_author_oracleclad_create_scenarioclad_link_capabilityclad_ingest_receiptValidates and create-only stores one signed portable receipt. Trust and expected digest context come from the registered host, never tool input.
clad_signoffRecords asserted audit or UAT history, and with verified: true and a registered issuer asks the human to confirm through an elicitation form before signing a portable receipt; without confirmation it returns HUMAN_REQUIRED.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
smol-toml: Denial of Service via malformed TOML documents
CLAD_HOST_SMOKETool annotations
20/27 tools have annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
27/27 tools missing one or more hints — clad_prepare_init (missing: openWorldHint); clad_stage_init (missing: openWorldHint); clad_init (missing: openWorldHint), +24 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.
Destructive tools are labelled
3 tools perform destructive updates without destructiveHint — clad_prepare_init deletes at line 565 (rmSync(path, {force: true})); clad_stage_init deletes at line 565 (rmSync(path, {force: true})); clad_prepare_clarify deletes at line 565 (rmSync(path, {force: true}))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
No hardcoded API keys
1 live-looking API key in source: 1 Stripe secret (live)
Move secrets to environment variables (process.env.X) or your secret manager.
Production dependencies are patched
0 critical, 1 high severity in production deps — smol-toml@1.6.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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.
[](https://m8ven.ai/mcp/qwerfunch/cladding)?variant=verified from the URL.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